this is not a Spring bug neither an AndroMDA bug, it is related to the way some reflection APIs used at runtime (such as commons-bean) resolve members based on the name
if the property name starts with a sequence of capitals the API gets confused, the behavior is different from the one found in the JDK to answer your other question: we prefer to restrict as much as possible class members as to improve encapsulation and reusability, but unfortunately the setter accessor needs to have a public visiblity since Spring uses it -- Wouter Zoons - [EMAIL PROTECTED] http://www.andromda.org/ _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=2417#2417 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user