Hi,
Some thoughts and questions.
When you talk about making "TM easier", are you talking about the
interface that the end-user see or are you talking about the Tuscany
developer who is trying to put together this functionality?
Today, in Java, TM is mostly about JEE and JEE makes heavy use of JNDI.
However, I have a concern that this is exposed to end-users (ie
programmers of business applications). SCA is trying to move away from
this kind of "plumbing in the application" to a model where the
programmer simply asks for what is needed and it is up to the runtime to
provide the facilities in whatever way it chooses. That is the
intent/policySet model.
So, if your intention is to design the TM implementation within Tuscany,
hidden from the end-users, then I can see the attraction, given that
most of the available TM software is based around JNDI. However, I hope
that this can be "hidden under the covers".
Yours, Mike.
shaoguang geng wrote:
Hello every one:
I make TM easiser, I think JNDI is the best way.
Please see it that most the java environment provide 2PC TM in a JNDI
infrastrusture, and most of the manageable resource such as hibernate and JPA
make this work if there is a TM binded in a JNDI.
To hold our TM in Tuscany's registry object just make every thing far from
fetching, because XAResource might be used every where, all of them will have
to get TM from an input parameter...
So I would suggest at the point of TM initialize, it could check out wether a
JNDI exists, and then bind it up on.
Thanks.
---------------------------------
Looking for last minute shopping deals? Find them fast with Yahoo! Search.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
