Should *ALL* entity beans use the MethodOnlyEJBLock policy, or just the
read-only entity beans? I was under the impression that only the read-only
entity beans should use this policy, but your comment about standardjboss.xml
below leads me to believe otherwise.
++jeff
On Wednesday 19 September 2001 07:37 am, Bill Burke wrote:
> MethodOnlyLock is there, but the read-only special case has not been put in
> yet.
>
> But,
>
> You can use the entity instance per transaction interceptors I wrote.
> Unfortunately there is a stupid bug in them in the 2.4.1 release, but you
> can get latest from the CVS Branch_2_4 to get my fixes.
>
> With "entity instance per transaction", entities are not locked into a
> transaction, but instead an instance per entity bean is created per
> transaction. To use this do the following:
>
> 1. Either change standardjboss.xml or create your own configuration as
> follows.
> 2. Edit the Standard CMP EntityBean (and/or BMP)
> 3. Search for <locking-policy> and switch it from QueuedPessimisticEJBLock
> to MethodOnlyLock.
> 4. Change EntityInstanceInterceptor to EntityMultiInstanceInterceptor
> 5. Change EntitySynchronizationInterceptor to
> EntityMultiInstanceSynchronizationInterceptor
> 6. Change <commit-option> to B or C.
>
> Regards,
>
> BIll
>
> > -----Original Message-----
> > From: Jeffrey Wescott [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, September 18, 2001 6:21 PM
> > To: [EMAIL PROTECTED]
> > Cc: [EMAIL PROTECTED]
> > Subject: MethodOnlyLock in 2.4.1?
> >
> >
> > Did MethodOnlyLock for read-only entity beans make it into 2.4.1?
> > If so, is
> > there any documentation on how to use it anywhere?
> >
> > ++jeff
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
