DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33228>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33228


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |




------- Additional Comments From [EMAIL PROTECTED]  2005-01-25 12:18 -------
(In reply to comment #2)
> If you check the BeanUtils API
> (http://jakarta.apache.org/commons/beanutils/commons-beanutils-1.6.1/docs/api/):
> 
> the required characteristics of JavaBeans that are important for most
> development scenarios are listed here:
> 
>     * The class must be public, and provide a public constructor that accepts 
> no
> arguments. This allows tools and applications to dynamically create new
> instances of your bean, without necessarily knowing what Java class name will 
> be
> used ahead

I saw the BeanUtils API document you refered, but I couldn't find
description that objects which BeanUtils processes must satisfyJavaBeans
specification. I'm sorry.
In addition, PropertyUtils.getProperty() works well for an object of package
scoped class which implements public interface which
has a getter method with *no argument*. If it is true that thislimitation is
spec of BeanUtils as you said, I can't understand why the case of methodwhich
has one or more arguments is not ok though the case of method which has no
argument is ok.

I attached another sample program to compare behavior of
PropertyUtils.getProperty(). This works well for method 'test2'
which has no argument, but it doesn't work well for method 'test'
which has one argument. (Please see test/T.java)


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to