OK, so, if I understand correctly, here's more or less how it works. Please
correct me if I'm wrong.
1. A client calls a method on an EJB. This method has a "Requires" or
"RequiresNew" attribute, so the container starts a transaction, and gets a JDBC
connection from the datasource/connectionPool.
2. This method calls another method of another bean located in another server.
The transaction context is propagated.
3. This method needs to make updates to the DB. Thus, it gets the connection
from the transaction context, and doesn't get a real JDBC connection, but a
proxy to the actual connection opened in the first server.
4. The proxy routes all the database operation to the connection opened in the
first server
Smart design, but does anybody have experienced any problem (exception
management, etc.) with this. Does it need any particular setting or driver (I
don't think so, but I could have missed something in the docs).
Also, I guess the performance penalty can be rather high (network traffic), and
putting all the beans potentially involved in a transaction in the same server
would be better. Which reasons might lead you NOT to colocate all these beans?
Thank you all for your help. I really appreciate it.
Regards.
JB.
--
Jean-Baptiste Nizet
[EMAIL PROTECTED]
R&D Engineer, S1 Belgium
Kleine Kloosterstraat, 23
B-1932 Sint-Stevens Woluwe
+32 2 200 45 42
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
