This means the entity will be read-only, i.e. write operations are not
allowed. But it is still locked in transactions.
AFAIK, you can use method-level read-only flag to avoid locking. Check
the dtd for jboss.xml for details how to set it up.
alex
Monday, March 03, 2003, 8:14:11 PM, Jon Swinth wr
I didn't mean to make the whole bean as read-only, just tell JBoss that get*
methods are read-only.
- Original Message -
From: "Jon Swinth" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, March 03, 2003 3:14 PM
Subject: [JBoss-user] Re: Deadlocks
> Does this mean that putting t
It does, but this is only affecting whether or not stores are not. This is not
changing whether or not the tx lock is acquired for method invocations.
There are two levels of services here, persistence and transaction serialization.
You need to mark the ejb and read-only or its methods in the jboss
two different things.
read-only for CMP means that updates will never happen.
read-only in jboss.xml is a container thing. You can either mark the entire
bean read-only, which means that the bean will never do any transactional
locking, or you can do it per method. See the JBoss for-pay docs fo
art of the documentation hidding?
>
> > From: "Bill Burke" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Subject: RE: [JBoss-user] Re: Deadlocks
> > Date: Mon, 3 Mar 2003 15:15:03 -0500
> > Reply-To: [EMAIL PROTECTED]
> >
> >
>
Start with the Read-Only Beans section on page 208
Scott Stark
Chief Technology Officer
JBoss Group, LLC
- Original Message -
From: "Jon Swinth" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, March 04, 2003 2:27 PM
Subject: [J
Chapter 5?
> From: Jon Swinth <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> Date: Tue, 4 Mar 2003 14:27:55 -0800
> To: [EMAIL PROTECTED]
> Subject: [JBoss-user] Re: Deadlocks
>
> I see the reference for read-only in the DTD, but I was advised that the docs
> had info on this. I don't mind
