On Tue, Jun 22, 2010 at 11:29 AM, ant elder <[email protected]> wrote: > On Tue, Jun 22, 2010 at 10:15 AM, Mike Edwards > <[email protected]> wrote: > > >> I've taken the first step on this one. >> >> binding.sca, binding.jms and binding.jms all now have >> @mayProvide="sca:asyncInvocation" in their definitions.xml files. >> > > Looking at keeping tuscany-binding-ws-runtime-jaxws-ri and > binding-hazelcast-runtime in sync with that and I wonder where should > those defintions.xml files go - in the runtime or model modules? > Presently for JMS its in the model module but for WS and SCA its in > the runtime module. If it can go in the model modules then i wont need > to do anything for tuscany-binding-ws-runtime-jaxws-ri and > binding-hazelcast-runtime. > > ...ant >
It depends on whether we think the two binding implementations will/may provide the same set of intents. They will at the moment but I don't know what the answer is in the longer term. I don't think there are any more imminent changes to the file (famous last words!). Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
