>From "JINI Transaction specification"
TX.2.2 Starting a Nested Transaction:
package net.jini.core.transaction.server;
public interface NestableTransactionManager
extends TransactionManager ...
Note that the "TransactionManager.create method returns a new top-level
transaction. Managers that implement just the TransactionManager interface
support only top-level transactions. Nested transactions, also known as
subtransactions, can be created using managers that implement the
NestableTransactionManager"
Ok your question is still valid though (almost :) essentially the EJB
transaction is nothing but a transaction. what is specific to EJB is how the
container manages the transaction demarcation for you based on the xml
descriptor you sent him. So it is a real transaction monitor that is
running under all these beasties. In JBoss we have built the architecture
so that we could plug in any transaction monitor. We ship "fastTM"
transaction monitor that works wonders in bean to bean communication inVM.
If you need "multiVM" or "Client-Server" communication then you need to
provide a distributed TM. We will probably try to integrate various vendors
and if the TM from JINI is good then we could integrate that as well to
provide you with these distributed transactions. But essentially the
plumber work is already in JBoss (although we haven't tested outside fastTM)
we could plug in a TM as an MBean and essentially use JINI nested
transaction from an EJB container :)
regards
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Filip Hanik
|Sent: Monday, January 22, 2001 8:26 PM
|To: jBoss Developer
|Subject: Re: [jBoss-Dev] bridgeEJB and JINI
|
|
|this is from the spec
|
|16.1.2 Transaction model
|The Enterprise JavaBeans architecture supports flat transactions. A flat
|transaction cannot have any
|child (nested) transactions.
|
|Filip
|~
|Namaste - I bow to the divine in you.
|~
|Filip Hanik
|Technical Architect
|[EMAIL PROTECTED]
|
|----- Original Message -----
|From: "Feng Wang" <[EMAIL PROTECTED]>
|To: <[EMAIL PROTECTED]>
|Sent: Monday, January 22, 2001 7:39 PM
|Subject: RE: [jBoss-Dev] bridgeEJB and JINI
|
|
|marc,
|
|No. I do not mean the other way around.
|
|Could you provide the reference that confirm that EJB does not support
|nested transaction?
|
|As to JINI, even though the jini API has the notation of
|Nested transaction, the Sun implementation of
|JINI Transaction Service "mahalo" does not support
|nested transaction at all.
|
|I am just wondering if what is the best way to bridge JINI and EJB in
|general. I think in the future both EJB and JINI will support nested
|transaction.
|
|Thank you for your input.
|
|Feng
|
|
|
|>From: "marc fleury" <[EMAIL PROTECTED]>
|>Reply-To: "jBoss Developer" <[EMAIL PROTECTED]>
|>To: "jBoss Developer" <[EMAIL PROTECTED]>
|>Subject: RE: [jBoss-Dev] bridgeEJB and JINI
|>Date: Mon, 22 Jan 2001 18:37:57 -0800
|>
|>|EJB TM supports two phase commit protocol and nested transaction.
|> ^^^^^^^^^^^^^^^^^^
|>
|>not that I know
|>
|>|JINI TM supported two phase commit protocol but only
|>|support flat transaction.
|>
|>Actually I believe JINI has nested transaction (pretty sure).
|>
|>maybe you meant the contrary?
|>
|>marc
|>
|>|Is there any ways to bridge EJB and JINI
|>|transactionally in JBOSS?
|>|
|>|Any inputs are welcome.
|>|
|>|thanks
|>|
|>|Feng Wang
|>|_________________________________________________________________
|>|Get your FREE download of MSN Explorer at http://explorer.msn.com
|>|
|>|
|>
|
|_________________________________________________________________
|Get your FREE download of MSN Explorer at http://explorer.msn.com
|
|
|
