Emerson Cargnin - SICREDI Servi�os wrote: > sorry for the simple question, but what's the difference if i use > homogeneous or heterogeneous deployment (regarding to distributed > two-phase-commit).
see below. > > how could I implement the follow: > > 1- access a method from a session facade from a client (this have > required transaction attribute on this method). > 2- the session facade finds and changes some cmp attribute. > 3- the session facade uses jdbc to change some data from legacy > 4- the transaction is commited ou relled back. > > Does this works using jbossTM? > If the session bean instance and the cmp bean live on the same JBoss server, transaction does not have to propagated, in such a case JBossTM will do just fine. The datasource to legacy will always be a local resource (since it has to be accessible by the session bean), so there will never be a need for transaction propagation there. All that the Tyrex plugin gives you is ability to propagate transaction from one JBoss server to another. Now, if I understand correctly, homogeneous deployment is when all the nodes in the cluster get identical deployments. In your case, this would mean that all the beans are on each and every node. In this scenario, a session bean instance that serves a request will always talk to its local cmp, so JBossTX will do just fine. Heterogeneous deployment is when, say your session beans are replicated across some nodes, while cmps are replicated across some other nodes. In such a case, you would have to be able to propagate transactional context across the nodes and need a Distributed TM like Tyrex. Can someone correct me if I am wrong? > obs: both cmp and legacy db are Oracle. > -- Anatoly ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
