Kohsuke Kawaguchi wrote:
>
> >
> > [1] except for the fact the impl.runtime classes are generated and not
> > part of a standard library. In our case we have a schema B that imports
> > schema A. The impl.runtime source files are now generated in the package
> > of schema B. The classes of schema A refer to the package of B, however
> > all classes of schema B lives in a child class loader of the loader
> > schema A. That means from the class loader of schema A its runtime
> > clases are not visible. I realize this is not a standard situation but
> > at least an option to specify where the impl.runtime classes are
> > generated would seems to be a nice option. I can work around it with
> > some extra lines of the build script, but I think having control would
> > be a nice feature.
>
> No problemo. Use the "-use-runtime" option.
>
I tried this (with a package name) but in that case I don't get any
impl.runtime classes, or at least not where I would expect them. Can you
show me how to do this. Both schemas get compiled by compiling schema B
and 2 binding files (for each schema 1).
--
Mark Brouwer