How can calling get instead of set be a 1.5 feature? The generics are 1.5 but how come Castor is not using the set methods? Why call get over and over again to add elements to the collection? This does not make sense and makes adding the attribute set-method useless.
-----Original Message----- From: Bill Leng [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 08, 2006 2:55 PM To: [email protected] Subject: Re: [castor-user] set-method that is jdk1.5 feature and castor does not use jdk1.5 yet, I guess. Jason Wood wrote: > Wondering what's the purpose of set-method attribute if the framework > calls getNames() to set the names member variable? > > > > So if I have ... > > > > Class myClass { > > private ArrayList names; > > > > public void setNames(ArrayList<String> names) {} > > public ArrayList<String> getNames() {} > > } > > > > > > How come Castor calls getNames() for each name it needs to add? Why not > Create and ArrayList<String> and call setName()? > > > > J > > > > > ------------------------------------------------- If you wish to unsubscribe from this list, please send an empty message to the following address: [EMAIL PROTECTED] ------------------------------------------------- ------------------------------------------------- If you wish to unsubscribe from this list, please send an empty message to the following address: [EMAIL PROTECTED] -------------------------------------------------
