Brian Pontarelli wrote:
> I figured this out I believe. I was using the same context for two
> packages, one with a namespace and one without. This was causing the
> context confusion, since the final Object graph I was marshalling might
> have contained Objects from the non-namespaced package.
>
> In addition, it was vital that my schema document had
> elementFormDefault="qualified" included, otherwise it looked like JAXB
> would only mark the root element with a prefix and nothing else.
The elementFormDefault="qualified" vs "unqualified" changes the meaning
of the schema drastically. This is one of the very confusing parts of
XML Schema.
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com