Mike Edwards wrote: >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".
I think that Mike is trying to say here that, it's OK to use JNDI, but as SCA comes to simplify things, this should be hidden. In this other post [1], it's mentioned a Hibernate scenario : >For example, users who used much of Hibernate. Hibernate is easy to config to >use XA Datasource from JNDI and TM as well. (But tuscany could not host any >implementation of Hibernate). >Does this mean users should have to abandon Hibernate? I'm sure this is not the >initiation of Tuscany. If I understood correct what Mike proposed, this scenario is still valid, the difference is that, it would be responsibility of the runtime (based on some configuration) to properly retrieve the TM using JNDI or not, and would make it available to other Tuscany modules such as implementation types, etc. This is similar to what we do today with BPEL, except that we are not using JNDI (yet ?) [1] http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg26385.html On Dec 12, 2007 5:30 PM, shaoguang geng <[EMAIL PROTECTED]> wrote: > Thank you for your reply, Mike: > > I agree with you, your words are correct! > > BUT, problem is: Tuscany needs more users, and Tuscany is not the biggest > gold, why users come to Tuscany? One of the reasons should be adaptability . > Users has big lot of technology in use before Tuscany (include JNDI). > > My proposal is just one of the ways that will make users fill easier to come > upon Tuscany's framework, Of course, there is better methodology like you > addressed here. > But most of the time, the best is not the most popular. > > Best regard. > > Mike Edwards <[EMAIL PROTECTED]> wrote: 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] > > > > > --------------------------------- > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it > now. -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
