|
Hi Ray elementFormDefault=”qualified”
affects only those elements which are local (i.e. declared within the context
of another element or type), not those which are global (i.e. declared at the
top level – just within <schema>). See http://www.w3.org/TR/xmlschema-1/ section
3.3.2. If you want the top level ones to not have
a namespace then you must not have a targetNamespace attribute in the <schema>
element. I believe your generated XMLBeans will
then end up in the “special” package “noNamespace”. But
please note - this is _not_
something we recommend. Namespaces are useful to stop your elements clashing
with ones with the same name from a different schema. Cheers, From: Roberts, Ray
[mailto:[EMAIL PROTECTED] I've got a schema that starts off like: <?xml version="1.0"?> But when I go to generate the xml from XMLBeans, my elements
all have prefixes attached to them. Does anyone know how to
generate unqualified XML elements via XMLBeans? Any help you could throw this way would be much appreciated. Thanks, -Ray |
Title: Message
- elementFormDefault="unqualified" not generated un... Roberts, Ray
- RE: elementFormDefault="unqualified" not gen... Lawrence Jones
- RE: elementFormDefault="unqualified" not gen... Roberts, Ray
- RE: elementFormDefault="unqualified" not gen... Lawrence Jones
- RE: elementFormDefault="unqualified" not gen... Roberts, Ray
- RE: elementFormDefault="unqualified" not gen... Don Stewart

