Hi all,
We have a server-side object which has to perform the following sequence
in its update() method:
- update the DB row it represents
- perform some communication with an external device
- update the DB row according to the success of the previous step
The two DB updates should not be performed in one transaction.
As far as I understand there are two design solutions:
1. implement this object as an Entity Bean using BMP in which
the object's update() method will explicitly perform the DB updates.
(and use TX_NOT_SUPPORTED for the update() method).
2. Use an entity bean to implicitly handle the object persistence
and wrap it with a statefull session bean which will perform the
logic described above.
It seems to me that the second option is preferable, but then
the question is how will the session been handle multiple
concurrent invocation of update() method keeping in mind
that the method does not make use of transaction to perform
the 2 DB updates.
Any comment will be highly appreciated,
Sveta
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
