The spec says that <include> takes the name of the composite to be
included but does not say how it should be located. We currently
support a scdlLocation attribute that takes a URL, with relative URLs
being resolved against the location of the containing scdl.
However, it would be nice to allow users to place SCDL somewhere on
the composite's classpath. I think we should also support a
scdlResource attribute that takes the name of a Java resource that
will be located using the same classpath as we use for Java classes
(i.e. the same classpath used to locate the class in a
<implementation.java> or <interface.java>).
One thing this would let us do is publish scdl fragments in the
kernel for things like the set of loader components (the current
loader.scdl) that can then be reused by the various hosts; this would
get rid of the duplicates and the need to maintain them. This will
help with the webapp host I am working on so I plan to add the
scdlResouce attribute soon.
The same would also apply to things like <implementation.composite>
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
