Hi Sebastien, One thing that comes to my mind is about the JavaRuntimeModuleActivator that also needs some modularization as we were discussing upon them some time back.
For your reference: On 5/29/08, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > > JavRuntimeModuleActivator is responsible for setting up the Java component > implementation runtime, allowing you to activate Java component instances > and dispatch to invocations from/to them. In theory it should be possible to > initialize the model, XML reader, and > introspection layers without bringing up the runtime layer. Unfortunately > it's probably not possible at the moment as the implementation-java-* > modules do not follow a clean layering... and mash > everything up starting in JavaRuntimeModuleActivator. > > So to summarize: > - JavaRuntimeModuleActivator mashes way too much together and should be > modularized > Thanks. On 6/3/08, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > > I'm starting to split some of the binding and implementation models in > separate modules, to allow their models to be used without dragging their > runtime dependencies. > > We've already done that on a number of them, I'm going to follow the same > pattern for the following modules as well: > - implementation-widget > - implementation-resource > - binding-http > - binding-ejb > - binding-jsonrpc > > This shouldn't break existing code as APIs/SPIs won't change. > > If there's no objections I'll commit these changes later this week. > -- > Jean-Sebastien > -- Thanks & Regards, Ramkumar Ramalingam
