On Jul 30, 2006, at 2:55 PM, ant elder wrote:
What about the dependencies of the extension? It looks like right
now all
the dependency jars still have to go in the boot directory and only
the
extension in the extension directory. Is that what you intend?
The spec does not define way to specify the classpath for a composite
so for now everything has to be bundled in it on in a parent
classloader (and the boot classloader is the parent to the each of
the extension composites).
The jar classpath will still work so if you provide a Class-Path
entry in the manifest dependencies specified there should be found.
Longer term I think we need a way to define a classpath in the
composite. I had a quick discussion a while ago with Oisin about
using a Maven repository to hold SCA artifacts and perhaps we can use
that here. I can think of two ways we could allow users to do this:
1) if the composite is provided as a jar file, look in the jar file
for Maven metadata stored in META-INF/maven/${groupId}/${artifactId}/
pom.xml and read the dependencies from there.
2) allow the user to specify a <dependencies> element in the SCDL
file listing artifacts to be added to the classpath
We take the list of dependencies, obtain them from a maven repo and
add them to the classpath for the composite. This would work for any
composite not just ones used as extensions.
Does that seem like it would work?
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
