Hi Steve,
I have had a look at the avalon-http-test.block file and reorganized the files of the demo application I am trying to deploy in Merling.
My block.xml file is as follows:
<?xml version="1.0" encoding="ISO-8859-1"?> <container name="service-separated">
<classloader> <classpath> <artifact>jar:/interfaces</artifact> <artifact>jar:/random-component</artifact> <artifact>jar:/identity-component</artifact> </classpath> </classloader>
First issue (my fault) ... the example I gave you was a cut and paste of an example I was working on under Merlin 3.3.1 which includes support for a consistent artifact spec. Merlin 3.3.0 does not support the spec format completely - so apologies there. Even so, there is a problem with the format your using - namely a missing group identifier.
First off - under Merlin 3.3.0 you should drop the "jar:" prefix.
Secondly, any artifact reference must contain a "group" and a "name" element. So for example - an artifact spec without a version reference within a classpath spec such as <artifact>fred/interfaces</artifact> translates to the repository location:
[repo-root]/[group]/[type]s/[name].jar
I.e.:
[repo-root]/fred/jars/interfaces.jar
So the first step is to get your interfaces.jar, random-component.jar and identity-component.jar into the repository cache (because that's where merlin will go looking for them when handling the creation of your container.
Cheers, Steve.
--
|---------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org | |---------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
