Philippe,
After studying the problem some more I want to simplify and restate. (Sorry)
Statement: Mutations to entity beans are not written to the DBMS until
end-of-transaction. Therefore, direct DBMS access after the bean mutation
and during the same transaction will not reflect the bean's state.
I am using a stateful session bean with a test-method having
container-managed txn attribute 'Required':
Step 1: find a BMP entity bean (identified by a method param) and call one
of its mutators,
Step 2: read the mutated table:row:column directly from the DBMS and find
that they are not the same (this step just happens to be another method in
the session bean).
When the test-method returns (a.k.a. end-of-txn), the beans ejbStore()
method is called
automatically by the container.
Is there any way to cause the container to update the bean immediately?
As I stated earlier, Weblogic had a vendor specific deployment option that I
used to make this work.
>I can try to reproduce your problem, but could you give more details ?
>As I understand, method A does find+update+call method B
>method B does find+get
>both methods are TX REQUIRED.
>is this correct ?
>--
>Philippe Durieux ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>Bull - 1 rue de Provence - 38432 Echirolles Cedex France
>[EMAIL PROTECTED]
>-> Download our EJBServer at http://www.evidian.com/ejb <-
>
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
