> -----Original Message----- > From: Stephen McConnell [mailto:[EMAIL PROTECTED] > 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.
Understandable. I also felt that passing the Appliance to extensions left things a little too open. I'll have to look into the Deployment Model more. > 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. I'll start playing around with some ideas. I would really like to see a nice extension API in Merlin. Thanks! J. Aaron Farr SONY ELECTRONICS DDP-CIM (724) 696-7653 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
