Jakob Praher wrote:
hi Steve,
thanks for all the supportive answers. The maven:jar bug is a very good pointer - I am currently doing a fresh compile.
Another impl question:
given a simplistic block:
<block>
<implementation>
<component name="fred"class="MyClass" activation="true"/>
</implementation>
</block>
and a classpath of: merlin-cli-x.y.z.jar
->How does the kernelloader/blockloader know about the dependencies, for instance, on commons-cli and excalibur-i18n?
Hi Jakob:
There are some implicit actions that merlin takes, and some aspects of the current implementation that you should be aware of. First, the implementation aspects - the classloader your component is currently provided with has all of the merlin container-side content in it. This is a temporary condition (side-effect of problems associated with the framework jar and its dependencies on logkit, and a few implementation issues). This will change. Generally speaking when declaring a block you should include *ALL* of the jars in the classpath defintion (including things like the framework) that you components needs.
Also you should be aware of that fact that Merlin will auto-include a jar or directory based on the command line argument. For example - execution of the following command automatically includes the target jar file in the classloader for the block under deployment:
$ merlin myAmazingSolution.jar
I've actually been working on a bunch of stuff which will make the classloader side a lot cleaner (i.e. a complete and total seperation of containment jars from client (component-side) jars - but more about that in another email.
Cheers, Steve.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
