RE: [JBoss-user] Are read only methods supposed to lock entity beans?

] [mailto:[EMAIL PROTECTED]]On Behalf Of Alice AdSent: Tuesday, July 09, 2002 10:18 PMTo: [EMAIL PROTECTED]Subject: RE: [JBoss-user] Are read only methods supposed to lock entity beans? Thanks Bill. A few more questions: 1. Will it work if method1 is read-only and method2 is not? (I

RE: [JBoss-user] Are read only methods supposed to lock entity beans?

Marking a method as RequiresNew, does not mean that the method is read-only, it just means that a new transaction must be started. Since the entity bean is already in a transaction the second call with hang. With JBoss 3.0, you can now define read-only methods, but I warn you, your test will

RE: [JBoss-user] Are read only methods supposed to lock entity beans?

Thanks Bill. A few more questions: 1. Will it work if method1 is read-only and method2 is not? (I guess) (The following question is not directly related to the 1st one) 2. My DB has an isolation level of READ_COMMITTED. Is there a way to enforce SERIALIZABLE at app server level? And if yes, does

RE: [JBoss-user] Are read only methods supposed to lock entity beans?

I meant "optimistic and pessimistic concurrency" not "optimistic and pessimistic locking".. Alice Ad [EMAIL PROTECTED] wrote: Thanks Bill. A few more questions: 1. Will it work if method1 is read-only and method2 is not? (I guess) (The following question is not directly related to the 1st