I'm using -javasource 1.5 the problem is that this generate getter List<YYY> but does not setter List<YYY> and i need the set, because i am using xmlObjects in Hibernate mapping , and in core hibernate they generate a persistSet that is puting in SET mapping.
do you know how i can do schemagen generate setters ? or why schemagen does not generate setters ?
To work around this im putting this code in generated class:
public void setVusuarioList( java.util.Set<org.apache.xmlbeans.XmlObject> set){
org.apache.xmlbeans.XmlObject[] array = (org.apache.xmlbeans.XmlObject[])set.toArray(new org.apache.xmlbeans.XmlObject[set.size()]);
setVusuarioArray(array);
}
Making it hibernate work fine with XMLBeans.
My appologies for my poor english, to help me I attached my source if can help to undestand what i can talk.
Thanks
Gustavo Aquino
Try compiling your schemas using scomp's –javasource 1.5 option, and in addition to the getXXXArray methods it will generate typed list getters List<YYY> getXXXList() and List<ZZZ> xgetXXXList().
Cezar
From: Gustavo Aquino [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 11, 2006 9:05 AM
To: [email protected]
Subject: Xmlbeans function setXXXList(Set or List)
Hi,
I'm using xmlbeans a long time. now i need to set a java.util.Set in XmlObject, we have getXXXList() to transform a arrayObjects in a List, why we dont have a setXXXList(Set or List) to transform list in arrayObjects ? Im work around to implement this in my build code, but i think that this is very util for more people.
Some one know why XMLBeans dont have this function in XMLObjects ? and if is really cool how i can suggest that this function is implemented in schemagen ?
Thanks.
Gustavo Aquino>>Register now for BEA World 2006 --- See http://www.bea.com/beaworld<<
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
