> I was stumped by the following post on TheServerSide:
>http://www.theserverside.com:8080/patterns/thread.jsp?thread_id=220#2665
>Gal suggests that most ejbServers will load multiple instances of an
>entity bean with the same primary key inorder to service multiple clients.
> Is this true? Which app. servers do this?
> He also suggests that serializeable transactions on these beans
won't
>really be serializeable, how is that possible? What does it matter what
>concurrency algorith is used, the spec says serializeable transactions must
>occur in a serial fashion, so thats all a developer should be concerned
with
>right?
>dazed and confused,
>Floyd Marinescu
This is true in the case of Option C beans in WebSphere.
WebSphere employs container managed serialisation for Option A beans but for
Option C beans, it delegates transaction isolation to the DBMS. It will
create
as many Option C bean instances for the same PK, in the same JVM as clients
ask
for. The DBMS must enforce transaction serialisation or conflict resolution
at
commit time.
Hamid
===========================================================================
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".
