>>> "9.1.10 Commit options" allows 3 options.
These options are fine for online users;
they preclude, however, the use of EJB for offline (laptop) users, where a
user gets data from the application server, takes his 3 days to do his
updates, and then submits his changed data to the container for update. The
spec says that container can choose between:
(1) keeping these beans locked for 3 days
(2) or preclude access to the database from different applications
(3) or else not cache at all.
In my opinion the container could perfectly well:
(1) not lock these beans
(2) let other applications happily access the database
(3) cache these beans anyway
If the container just makes sure to re-read these beans before update and
compare to what was originally read (three days ago, original beans to be
re-submitted along with changed beans), and only then apply the changes or
throw an exception.
Does anybody know why this option was not retained in the specs?
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
