Bill Burke wrote:
> Vinay,
>
>
>
> I'm pretty sure the EJB spec says that an instance of an EntityBean can
> only process one request at a time. I think this is what the Context
> lock is for.
>
>
>
> When you say that your bean is readonly, you mean that you defined it in
> JAWS as readonly? I'm pretty sure the code does NOT check to see if the
> EntityBean is JAWS and therefore doesn't check to see if it is readonly.
I'll confirm that. the JAWS readonly stuff is confined within JAWS.
>
>
>
> IMHO, there should be an option to remove EntityBean locking and let the
> Database handle the synchronization either through the select-for-update
> option, or doing the locks in BMP.
>
I'd tend to agree, but that we'd also have to allow multiple instances of
a bean in memory in order to gaurentee the proper threading behavior. This
would improve throughput on scenarios with small datasets and large
numbers of concurrent users.
-danch
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
