Just to give more information about the use case. The target ejb2 cmp bean method is performing a read-only batch operation on many rows in the database (get application user group membership list).
This method is marked with "@ejb.transaction type=NotSupported" and the bean has row-locking=true.
I'm thinking that the row-locking should be disabled for this case since there is no active transaction.
This is an edge case but I think its worth addressing. I'll Jira it and fix it if there is agreement that its safe to fix. I didn't want to Jira it if were not going to fix it.
Thanks,
Scott
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4046639#4046639
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4046639
I have Seam 1.2 successfully running on WAS 6.1. I recreated the error you see when I place the seam jars into the EAR. If I have the Seam jars in the WEB-INF lib directory only, the error is cleared.
In my implementation I am running JBoss Rules BRMS 4.0. To get it running I created an EAR in RAD, then created a Dynamic Web project and copied in all of the JBoss Rules BRMS 4.0 war (uses Seam 1.2) files. I deployed the ear and it works without any other modifications.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4046636#4046636
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4046636