> 1) Availability of XJC as an API.
> I see a need to compile XML schemas programmaticly and use the result
> classes and objects immidiatly. To do this now, a runtime.exec call to
> xjc is needed and the compile results are "learned" using a class loader.
> This is quiet cumbersome for what I am trying to achieve.(And not fully
> implemented yet).
Well, like you said, you can do that today by using the runtime.exec
method. Given the absence of the javac API today, even if JAXB supports
a standard compiler API, you still have to rely on runtime.exec for
javac.
Plus if you are asking for a standard JAXB compiler API, it clearly
calls for an EG decision, and we just finished the JSR-31!
If you are looking for an entry point to XJC, then you can use:
public static int com.sun.tools.xjc.Driver.run(
String[] commandLineArguments,
PrintStream statusOutput,
PrintStream errorOutput)
throws Exception
We are not committed to this "API", so think of this as a backdoor that
could break anytime. This hasn't changed since the day one we started
JAXB RI, but we reserve the right to change it.
> In general my interrest boils down to Schema Object Models and practical
> experience/samples to use them.
Stay tuned...
regards,
--
Kohsuke KAWAGUCHI 408-276-7063 (x17063)
Sun Microsystems kohsuke.kawaguchi_at_sun.com