I'm trying to deploy Merlin as an embeded container running in a J2EE environment. For the moment I'm boostrapping the Kernel in the Web tier, passing it the context classloader as both Merlin common loader (urn:merlin:classloader.common) and Merlin system (urn:merlin:classloader.system) loader.
What is the exact role of these two classloaders (common and system) ? Where is Merlin looking for component to be deployed ? I mean, if I declare a given component in the block file, where should that component be located ? I guess there are different locations available, but I cannot figure them out from the documentation. I thought Merlin would scan all available jars using the different loaders it is given, but this seems to go wrong in a J2EE context... I had to explicitely declare the extended classpath in the block.xml file, otherwise the DefaultTypeRepository could not find the component type. As the block file contains the classname of the component, I expected Merlin to ba able to load both the component definition and the class with the classloader it is provided. So what is the exact process when Merlin tries to populate its type registry with component types, and how does it relate to the classloaders it is given during bootstrap and the extended classpath of each container ? Laurent ************************************************************************ Ce message a ete inspecte par un anti-virus Nous vous rappelons que la taille des messages ne doit pas depasser 1.5 Mo ************************************************************************ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
