I have not worked on the latest DAS-SCA integration so far, and am quite sure Lucinao will have good pointers in this area. But looking at the current tuscany-implementation-das, can see the following possible. So take this as my attempt to understand intents/policySets and DAS-SCA integration :)
DASImplementation implements org.apache.tuscany.sca.assembly.Implementationand contains org.apache.tuscany.sca.assembly.Service dasService. Using dasService, requiredIntents on the Service can be found. org.apache.tuscany.das.rdb.DAS interface can be enhanced to accept these intents. DAS internally can configure DASConfig reflecting the intents specified , so that DAS instance construction happens with correct attributes. Based on these attributes DAS transaction control will occur (if intent is TransactionControl). Intent TransactionControl can be qualified as say, 1) Container Transaction Control, 2) DAS Transaction Control. Advantage of having intent attached to a service will be, using different intents for different services of same component. Questions: What will be the policySets here? Say, if policySet/intent "Container Transaction Control" mandates that the implementation should expose getConnection() so that container Runtime can use it, how this mandate can be achieved? When DAS is not running as part of SCA runtime, DAS Config will support required equiavalent attributes thru DAS Config. Regards, Amita On 8/21/07, haleh mahbod <[EMAIL PROTECTED]> wrote: > > Aligning the two transaction handling model makes sense specially when > there > is support for a generic DAS as an SCA service. There has been some > discussions on DAS as a service on the mailing list in the past. > > On 8/20/07, Mike Edwards <[EMAIL PROTECTED]> wrote: > > > > Folks, > > > > Sorry to cut across the discussion about Transaction support in DAS, but > > are folks aware of the proposal for Transaction support in SCA? > > > > ....which leads to the entertaining question of how the DAS transaction > > support relates to the SCA transaction support. > > > > The problem at the moment is that the SCA spec group only has an > > unpublished draft of the Transaction support spec. The intention is to > > publish an updated draft in the near future. > > > > However, I can say that the SCA spec mechanism is based on the use of > > Intents to apply transactional characteristics to SCA components. > > > > > > Yours, Mike. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
