On 3/13/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
ant elder wrote: > On 3/11/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > > <snip/> > > To help explore these ideas, I'm thinking about starting some concrete >> work and try to pull some of the kernel code into individual modules, >> probably start from the bottom of the stack and have the assembly >> metadata and SCDL loaders in separate modules. There's a lot of code, so >> I could use any help if people are interested. > > > > I'd like to help, could you say a bit more on some specific things to > help > with that would fit in with what you've already begun? > > ...ant > Ant, Here are a few features that could packaged as separate modules IMO: - language independent interface definition support, independent of WSDL and Java (the *idl* packages) - support for SCA contributions - core databinding framework - builder framework - wiring logic - IOC injection container - lifecycle management - invocation/message interceptor framework - federated deployment and distributed wiring in an SCA domain - <implementation.java> support, annotation processing, and scope management - policy support Just pick what you're interested in, but I think it'll be easier if we get the top ones in place first. IIRC you've been doing some work with WSDL/Java mapping so the interface definition (idl) framework may be a good candidate, starting with creating a new Maven module for it...
Ok, I'll start having a look at this language independent interface definition support. ...ant
