Peter Courcoux wrote:
Hi all,
I'm looking at using merlin in a webapp environment and considering the
location of the set of components that merlin should manage. Is there
some standard on this?
I'm considering a hierarchy something like :-
WEB-INF/avalon-components/component1/classes/BLOCK-INF/block.xml WEB-INF/avalon-components/component1/classes/package/component1.class WEB-INF/avalon-components/component1/classes/package/component1.xinfo WEB-INF/avalon-components/component2/classes/BLOCK-INF/block.xml WEB-INF/avalon-components/component2/classes/package/component2.class WEB-INF/avalon-components/component2/classes/package/component2.xinfo
Looks fine.
WEB-INF/avalon-components/component3/component3-1.0.jar
This one will be problamatic if the deployment path is a jar: url. If its a file url then everything will be fine. The problem is that the URLClassLoader in the JVM does not handle jar files embedded in a jar file using the jar: protocol.
I would anticipate that the root, in this example WEB-INF/avalon-components, could be an initialization param set in the web.xml file.
Has anyone any thoughts, preferences or comments on this.
I'm try to think ahead in terms of seperating the merlin embeded kernel the web application - but thoughts are a little too random just at the momement. I'm confident that a lot of things will become clearer as start dealing with implementations.
Cheers, Steve.
Regards,
Peter
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
