Hi,
Take a look at the "Instance Per Transaction CMP2.x" configuration settings in standarjboss.xml. o You can make your EBs use that configuration by setting the <configuration-name> element in your jboss.xml. o You can mark your EB readonly. o You can mark certain methods of the EB read-only. Look through the jboss.xml DTD. Moreover, in JBoss3.0.3 there is a NoLock locking policy (MethodOnlyEJBLock has been deprecated/removed in that release), as well as a SimpleReadWriteEJBLock class, but I could not find any documentation that (except the source code, of course). Maybe this gives you a start. Regards Georg -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Horia Muntean Sent: Monday, October 07, 2002 11:19 To: [EMAIL PROTECTED] Subject: [JBoss-user] How to avoid entity beans read lock ? Hello all. I am using "A" <commit-option> on a Standard CMP EntityBean container. I was wandering if there is any way to avoid the locking of the EB(entity beans) when one (i.e session bean) calls get* methods (read-only) upon them. Any help would be appreciated. Thanks. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
