RE: Problems with namespace prefixes in version 2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday, May 24, 2005 4:38 PM, Radu Preotiuc-Pietro wrote: > This is one nitpicky customer! What prefix exactly does he > expect? It is for this kind of cases that we introduced > XmlOptions.setSaveSuggestedPrefixes().

RE: Problems with namespace prefixes in version 2

you really get to generate documents that are GB in size in practical situations? Thanks, Radu -Original Message- From: Jim McMaster [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 24, 2005 3:23 PM To: user@xmlbeans.apache.org Subject: RE: Problems with namespace prefixes in version 2

RE: Problems with namespace prefixes in version 2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday, May 24, 2005 4:17 PM, Lawrence Jones wrote: > Hi Jim > > One further thing. The prefixes used in the schema document and the > prefixes used in the instance document do not have to be the same. > The only thin

RE: Problems with namespace prefixes in version 2

#x27;t use the XmlBean itself to produce the instance document? Cheers, Lawrence > -Original Message- > From: Jim McMaster [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 24, 2005 1:54 PM > To: user@xmlbeans.apache.org > Subject: RE: Problems with namespace prefixes in version

RE: Problems with namespace prefixes in version 2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday, May 24, 2005 2:43 PM, Lawrence Jones wrote: > Hi Jim > > I can answer your first question. I'll have to leave someone else > to answer your second. > Thank you for the explanation. I am a novice at schema,

RE: Problems with namespace prefixes in version 2

Hi Jim I can answer your first question. I'll have to leave someone else to answer your second. Your schema defines a targetNamespace of "http://www.aptas.com/ontology";. datafeed is defined as a top-level (i.e. global) element. This means that instance documents need to refer to that element usi