One scenario where this would come to hand is to be able to load a SCDL, but let the java interfaces and implementations to be loaded on a second phase. At the moment, I'm just going ahead and processing and loading all at once.
-- Luciano Resende http://people.apache.org/~lresende On 2/20/07, Jeremy Boynes <[EMAIL PROTECTED]> wrote:
On Feb 20, 2007, at 2:56 PM, Luciano Resende wrote: > Jim wrote: >> Based on some of the deployment work that will be done, we actually >> need to separate out the load phase into two, one which loads the >> assembly model and another phase which resolves the dependencies >> necessary to construct the component type metadata (e.g. Java class, >> WSDL, etc.). I think we should pick this work up once we have those >> phases separated out. > > Jim or Jeremy, could you guys please let me know what's the status > of this > separation ? I'm in need of this for the contribution services, to > be able > to process a SCDL without necessary having to load dependencies on > the first > pass. I'd started on factoring this out by deferring resolution until the build face but ran into a problem with ServiceContract where we were relying on the Java interface being present. I moved on to other things ... What's the issue? Can't we just continue to load the dependencies for now? -- Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
