No, in 3.0 and 2.4.1 it is a locking-policy. In 3.0 or 2.4.1 look in
standardjboss.xml, search for locking-policy.
Bill
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> Ferguson, Doug
> Sent: Thursday, September 06, 2001 2:44 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: [JBoss-dev] TRANSACTIONS
>
>
> So I take it that MethodOnlyLock is a transaction setting?
>
>
>
> -----Original Message-----
> From: Bill Burke [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 06, 2001 12:52 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] TRANSACTIONS
>
>
> Right now, you can use the MethodONly Lock, but I haven't made changes to
> jboss.xml so that you can mark an entity as read-only and the
> EntitySynchInterceptor will behave differently.
>
> Bill
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of marc
> > fleury
> > Sent: Thursday, September 06, 2001 1:37 PM
> > To: [EMAIL PROTECTED]
> > Subject: RE: [JBoss-dev] TRANSACTIONS
> >
> >
> > |There is a MethodOnlyLock that you can put in for read-only
> beans, but I
> > |eventually want to extend this so that read-only beans never
> > become part of
> > |the transaction.
> >
> > interesting, and all configurable in jboss.xml yes?
> >
> > marcf
> >
> >
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-development
> >
>
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
