Mike Rubin wrote:
>
> Phillipe Durieux wrote:
>
> >No, it's a misunderstanding. It's true that in the client process, the
> >Current
> >class is local to the process. Only when the client will call a remote bean
> >the transaction become a distributed transaction. The implicit propagation
> >of the
> >transaction context insure that the bean will be aware that a transaction has
> >started, so the trace you see in the server then is normal.
>
> I don't think I'm seeing the transaction propogation. Specifically, I'm
> seeing a failure in the session bean client example. The relevant client
> code is:
>
> utx.begin();
> t1.buy(50);
> System.out.println("Rollback the transaction");
> utx.rollback();
>
> val = t1.read();
>
> The call to t1.buy() appears to start and commit a new transaction rather
> than using the transaction started by utx.begin(). Thus, when t1.read()
> is called, the returned "val" is 50 more than expected. Following is the
> trace with annotations from the corresponding source.
>
> Thanks for your help.
>
> - Mike Rubin
> - Modulo Systems Corporation
>
> ==================================================
>
> // utx.begin(); // No trace from this call
>
> // t1.buy(50);
> JOnASOpBeanOp.buy()
> JBeanSession.preinvoke()
> Transaction Attribute = TX_REQUIRED
> Current.getTransaction()
> Method called outside a transaction scope : begin a transaction
Hi,
it seems that the propagation context is not propagated.
I don't know if we have already use JOnAS on Mac.
Can you please run GenIC with the -keepgenerated option and send us
for examples :
JOnASOpBeanOp_Stub.java
JOnASOpBeanOp_Stub.java.save
JOnASOpBeanOp_Skel.java
JOnASOpBeanOp_Skel.java.save
I would like to verify the stub/skeleton generation is correct
thanks
--
Philippe
Philippe Coq Groupe Bulll/BullSoft/OpenMaster Phone: (33) 04 76 29 78
49
Bull S.A - 1 rue de Provence - 38432 Echirolles Cedex France
[EMAIL PROTECTED] http://www-frec.bull.com
Download our EJBServer at http://www.bullsoft.com/ejb
