Hi,
Are you proposing to use JNDI to host the managed objects such as TM and
XAResource? Do you expect the resources be made available to component
implementation code (for example, via dependency injection)? Please
elaborate. A few use cases will be really helpful.
To bind TM to JNDI, there might be multiple cases.
1) The TM has already been bound to JNDI provided by the hosting
environment, for example, embed Tuscany with Geronimo.
2) JNDI naming service is provided as a system service for Tuscany, and TM
can be bound to it.
Thanks,
Raymond
----- Original Message -----
From: "shaoguang geng" <[EMAIL PROTECTED]>
To: <tuscany-dev@ws.apache.org>
Sent: Sunday, December 09, 2007 6:02 PM
Subject: I wish Tuscany would bind TM to JNDI
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]
