Yes, I think I have it working essentially based on your explanation below. I think I was getting hung up on the relationship and navigation between the 2 AddressDocuments.
Thank you for taking the time to making sense of it. Peter ________________________________ From: Radu Preotiuc-Pietro [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 05, 2008 8:07 PM To: [email protected]; [EMAIL PROTECTED] Subject: RE: xsdConfig general question(Long) Peter, Have you found the answer to your second question? It's a bit confusing because you have one type and two elements all called "Address" but in AddressDocument there is a method addNewAddress(). Call that and you get the "outer" (root) <address> element. Then on the AddressDocument.Address object returned by this call, do addAddress(String). That adds the "inner" <Address> element. That's all there is to it. Radu PS Only use AddressDocument2 if you want <Address> to be a root element itself; then, since the type of the element is xs:string, it makes sense that it will ask for a String as argument. ________________________________ From: Peter Adelmann [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 05, 2008 10:45 AM To: [email protected]; [EMAIL PROTECTED] Subject: RE: xsdConfig general question(Long) Cezar, Thanks very much for answering the post. Your answers are helpful!! Peter ________________________________ From: Cezar Andrei [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 05, 2008 1:29 PM To: [email protected] Subject: RE: xsdConfig general question(Long) Hi Peter, I've put together some examples on the following page: http://wiki.apache.org/xmlbeans/XsdConfigFile But as specified the definitive structure is in the file that describes the schema of xsdconfig files: http://svn.apache.org/viewvc/xmlbeans/trunk/src/configschema/schema/xmlc onfig.xsd?view=markup Cezar ________________________________ From: Peter Adelmann [mailto:[EMAIL PROTECTED] Sent: Friday, August 01, 2008 11:40 AM To: [email protected] Subject: xsdConfig general question(Long) Hi, First off there's a lot of really good information gained by searching these groups on keywords, which I've done. Simple question#1: Is there some sort of manual or list of the xsdConfig stating what can be included in this file, the syntax, and the general types of things you and can't do with this file? It seems to be some sort of alchemist's incantations to try and figure out. Question #2: I have a snippet of a schema which is causing problems with sComp; <code> <xs:complexType name="address"> <xs:annotation> <xs:documentation/> </xs:annotation> <xs:sequence> <xs:element ref="s:address"/> </xs:sequence> </xs:complexType> <xs:element name="address"> <xs:complexType> <xs:sequence> <xs:element maxOccurs="unbounded" ref="s:Address"/> <xs:element minOccurs="0" ref="s:City"/> <xs:element minOccurs="0" ref="s:State_or_Province"/> <xs:element minOccurs="0" ref="s:Postal_Code"/> <xs:element minOccurs="0" ref="s:Country"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="Address" type="xs:string"> <xs:annotation> <xs:documentation>One or more lines of address information</xs:documentation> </xs:annotation> </xs:element> </code> This creates AddressDocument and AddressDocument2 and an Address. However the only element I can access when trying to build xml from this is Document2 Address, which contains a setAddress(String). I don't think this will work; I'm pretty sure I need to access the AddressDocument.Address and set the elements, however this doesn't seem to be available to the parent item, only the AddressDocument2. Is there a way to put something into the xsdConfig to re-route this relationship? I've tried <xb:qname name="s:address" javaname="addressType" /> <xb:qname name="s:Address" javaname="addressString" /> It didn't seem to help very much. I'm pretty new to xmlBeans, have used JaxB, but it wouldn't let me bind the schema. I'm hoping it's inexperience at this point. Unfortunately I can't change the xsd. Thanks for any assistence, Peter
