Hi Kohsuke,
Thanks for your response, comments inline:
On 9/28/06, Kohsuke Kawaguchi <Kohsuke.Kawaguchi_at_sun.com> wrote:
>
> In 2.1, we can do a separate compilation like that. See
> http://weblogs.java.net/blog/kohsuke/archive/2006/09/separate_compil.html
>
> But even when you do that, XJC still needs to see the whole schemas.
I've read your blog, but I'm still going to be stuck as the best I can
do is get WSDL. I'm assuming that there's absolutely nothing I can do
without a static schema to reference?
Is it theoretically possible that JAXB might be able to be modified so
that I didn't need the schema? Ie, if I gave xjc a reference to the
ObjectFactories and classes/packages that it should use, then it could
get to an element and go, hey, I already have a compiled class for
this QName, I'll use that. I realise that currently this is coming
from the parser, but if the parser was given an entity resolver that
used the above logic, this would in theory work wouldn't it?
I'm not asking for this to be done, just trying to make sure I
understand where the limitation is.
cheers
dim