Joe Barefoot wrote:
> If jBoss does not support distributed transactions, does that mean that all
> transactional attributes are lost when a call is made to a bean running on
> another server?
Well, the transaction is lost only when you get
the "cannot import" warning. The transaction
context is propagated to the other VM, but the
current TM implementation used in JBoss does not
have the network communications needed for a real
distributed TM. So when it is detected that the
transaction was started in another VM the local
TM gives this warning instead of importing.
> i.e., transaction checks are no longer made on any methods belonging to said
> bean, or any methods (its own or another bean's) that it uses to complete a
> method call?
> is this correct?
The second VM works like any other VM running
JBoss.
Only issue is importing transactions that
originates from another VM.
So if you call from the first VM to the second
VM without a transaction context, you will have
no problems.
Best Regards,
Ole Husgaard.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
