Thanks for looking into this. If you are right, then if any customization
is needed, the reference implementation of JAXB cannot generate classes for
a namespace that is defined in a collection of .xsd files using <xs:include>
elements. CIP4 decided to use that approach for the
http://www.CIP4.org/JDFSchema_1_1 namespace because the namespace definition
is so large. I'll try combining all of the .xsd files into a single file
and see what happens.
--Judy
-----Original Message-----
From: Kohsuke Kawaguchi [mailto:Kohsuke.Kawaguchi_at_Sun.COM]
Sent: Friday, September 19, 2003 12:17 PM
To: users_at_jaxb.dev.java.net
Subject: Re: Customization and XPath Expressions
I looked at the schema, and indeed JDF.xsd didn't contain the
<xs:attribute name="Class" /> attribute. You have to specify the right
file.
I guess you misunderstand XPath --- it works on XML documents as infoset,
it doesn't understand the concept of <xs:include>s.
regards,
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
For additional commands, e-mail: users-help_at_jaxb.dev.java.net