posted 18 years ago
Possibly because the object is not [i]exactly[/] a bean - maybe a getter or setter is not public, or the required typse don't match. Look at the stack trace to see which property of the bean is accessed when the exception is thrown, and then check the methods related to that property.
If that doesn't help, post the stack trace, and a short, relevant excerpt from the bean, and we'll take a look at it.