Farr, Aaron wrote:
Hello.
Okay, I've finally had some time to dig into merlin 3.0. I'll probably have a number of questions and patches over the next couple of days.
First question: Is there any replacement in 3.0 for the DeploymentStageExtension which was in merlin 2.x?
Nope - the intention is to replace it with something that passes a DeploymentModel instance instead of an Appliance. The problem with passing an appliance is that it exposes too much info to the extension. Secondly, there has been some shuffling of things around at the level of the kernel - now the kernel creates a root container and I'm thinking about how we can use this to locate privaliged componenents (such as extensions). One of the issues you should aware of is that if you deploy an extension with access to a model, we need Merlin to provide the privaliged classloader. Currently the classloader provides nothing more than the APIs and privaliged content needs the SPIs as well. This means when Merlin locates an extension - it needs to provide the extension with an extended classloader.
I.e. some non-trivial thinking needed ... each container needs to supplied with an API and SPI classloader. Currently we are only dealing with the API case. This means some thinking and additions to the DefaultClassLoaderModel implementation.
Stephen.
J. Aaron Farr SONY ELECTRONICS DDP-CIM (724) 696-7653
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
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]
