RE: Namespace prefix throws spanner in works

A question about xmlbeans: if I change the schema locally and compile my xmlbeans into a jar, is that elementFormDefault attribute ( all schema info) compiled into my jar, or will xmlbeans validate() try to reference the schema again? In my current set-up in Eclipse, I am certain that the app is

Resent: xs:all fails to validate minOccurs='0'

For schema: xs:complexType name=Invoice_Type xs:all xs:element name=InvoiceNum type=INV_NO_Type minOccurs=0/ xs:element name=InvoiceClass type=INV_CLASS_Type/ xs:element name=Warehouse type=WARE_NO_Type/ /xs:all /xs:complexType Where INV_NO_Type is defined as an Integer,

RE: Namespace prefix throws spanner in works

Hi Adam Re your question on which elementFormDefault applies (1) or (2) - unfortunately for you it's the one in the schema element surrounding the local declaration of mediumName in the scheduleNameGroup model group definition. So the unqualified treatment required by (2) is correct. I have some

RE: Namespace prefix throws spanner in works

Hi Adam scomp has an option, -dl, which will download included and imported schemas from the network. In the absence of this option no network downloads take place and it searches for includes and imports locally. I'm not sure of the details of exactly how this works but if you are compiling

RE: good way of writing xs:any

XmlCursor's copy and move methods can be used for this. -Original Message- From: Ali, Haneef [mailto:[EMAIL PROTECTED] Sent: Monday, May 23, 2005 5:38 PM To: user@xmlbeans.apache.org Subject: RE: good way of writing xs:any Hi Steven, This is one area where the functionality of