Hi Raymond I can help with the first item, related to SCA Domains. I'm working on getting the contribution model object to return a list of deployable composition, but when I tried to integrate into the runtime, I really felt the necessity of the SCA Domian. Have you already started something on this area?
On 4/19/07, ant elder <[EMAIL PROTECTED]> wrote:
On 4/18/07, Raymond Feng <[EMAIL PROTECTED]> wrote: > > Hi, > > I'm thinking of improving and simplifying the runtime further in the > following directions: > > 1. Have the Tuscany runtime to maintain the SCA domain composite and > refactor the DeployerImpl into the Domain service. > > 2. Simplify the relationship between runtime metadata > (o.a.t.spi.Component/Service/Reference) for the invocations and model > (o.a.t.assembly.*). > > 3. Improve the Wire/InvocationChain to support dynamic style invocation > (in > cases that we don't know or don't care about the interface/operation until > runtime) in addtion to the operation-based invocation chain. > > 4. Implement the CallableReference/ServiceReference/CallbackReference. > > The list is not meant to be complete. Please feel free to add your ideas. All those sound good to me, I'm particularly interested in 3 for the script implementation so I'd like to help with that one to make sure it does what I need. Will have to wait a day or two while I get the script implementation more fully functional. ...ant
-- Luciano Resende http://people.apache.org/~lresende
