Hi again,
before i leave in the weekend, i wanted to report another problem (that i
encountered after changing the jndi name of the databases in my bean managed
beans ;-).
I have a bean type T and create two beans (from a remote client):
A = T.create
-> should start a new transaction
-> ejbCreate -> INSERT into table
-> should commit transaction
B = T.create
-> should start a new transaction
-> ejbCreate -> INSERT into table
-> should commit transaction
A.setSomeVarThatDependsOnABean( B );
-> should start a new transaction
-> ejbFindByPrimaryKey(B) -> SELECT
-> B.callSomeBusinessMethod()
-> B.changeSomeValue()
-> A.setTheVar()
-> A.ejbStore -> UPDATE
-> B.ejbStore -> UPDATE
-> should commit transaction
Until here everything seems ok. But the transaction of the
A.setSomeVarThatDependsOnABean( B ); seems never to be commited. Neither the
values changed in A nor in B are written to the database.
If i use the "raw" datasource instead, everything works fine (probably
because there's no transaction handling at all for the DB in this case ;-).
Note that there's no exception, neither on client nor on server side.
And (that's strange, too) after this the server loads both bean A and B with
ejbLoad, though there was no client request (but this happens with both
datasource variants and has no negative effects).
This happens with 0.9.4. I stopped testing with other versions (like
0.9.4v), for the sake of the ejbPassivate problem mentioned a few days
before.
Best regards, nice Weekend
Jens Stutte
____________________________________________
[EMAIL PROTECTED], http://www.net-media.de
NetMedia GmbH
Schubertstr. 8
66111 Saarbruecken
Germany
fon: +49 (0) 681 - 37 98 80
fax: +49 (0) 681 - 33 89 3
