wood burning stoves 2.0*
The moose likes EJB and other Java EE Technologies and the fly likes Deployment strategy and transactions Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Deployment strategy and transactions" Watch "Deployment strategy and transactions" New topic
Author

Deployment strategy and transactions

Jeff Wisard
Ranch Hand

Joined: Jan 07, 2002
Posts: 89
I have an Stateless Session Bean that has defined all of its methods to require a transaction (transaction set to 'Requires'). I fully expect the client bean of this bean to begin a transaction before calling the methods of my bean. What I am not sure of is how this will work if my bean is deployed in a separate ear file than the client bean.

That is, will my session bean be able to use the transaction started by another bean that calls my session bean remotely from a different deployed ear? Or do they have to be deployed wihin the same ear file for my session bean to use the transaction?

How does this work in a clustered environment?


Jeff Wisard<br />Sun Certified Java Programmer (Java 2)<br />Sun Certified Web Component Developer
Nathaniel Stoddard
Ranch Hand

Joined: May 29, 2003
Posts: 1258
Transactions are propogated from client to server, etc. So, any client of your EJB app will be able to work correctly, regardless of whether the client is another EJB app or a simple non-J2EE app like a rich-client.


Nathaniel Stodard<br />SCJP, SCJD, SCWCD, SCBCD, SCDJWS, ICAD, ICSD, ICED
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: Deployment strategy and transactions