I have made the change that allows mediators to implement init(SynapseEnvironment) and destroy().
In order to do this I created a new Interface ManagedLifecycle with those methods on it. I haven't yet figured out how to support this for the dynamic registry updates, but init and destroy are called everywhere else. I've also created a new top level element in <definitions> <startup> Any children of this must have a StartupFactory registered. This works the same was as MediatorFactory. I will send a separate note about the Factory model we are using. I have written a QuartzStartup and factory, which I will checkin separately. This uses this to get started. I've also made significant changes to the Class mediator. It no longer uses dynamic properties. Basically you can set String and OMElement properties and they get set at startup. This is because they need to be set before init() is called. I explained in another note why I don't think we need dynamic properties on a class mediator. (ps. I think I've broken the Unit tests :( Can someone help me fix them up please!) I also haven't yet fixed the CM serializer. As regards the Thread Pool, I think we need to fix this. For the moment I'm just using new thread pools rather than those provided by Axis2. I don't know how well this would work if we were running in a container instead of just as our own server. I've also changed the SE.createMessageContext() to automatically add an Envelope and Body, because it makes life much easier. Paul -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
