Don't know if it helps but consider this explanation: When you call upon an entity with some kind of getCollection and receive a collection of locals of another bean you performed a transaction. If you have not opened a transaction outside this call context, say in a session bean, you performed this get in it's own transaction which ended when you finished the get. So now when you try to manipulate this collection it is already outside the transaction context. So, if you make your entity transaction requiered it's not enough, it only states that when you call upon the entity you use a transaction, a transaction is opened for each call separatly.
If you don't want this behavior (and obviously you don't) your best bet is to open a transaction before you manipulate the entity bean and its relations, thus when operating within transaction context the container will not open a new one, and only close it after you finsihed everything you want to do. The easiest way to do this is to use a session bean facade. Open the transaction on the session bean which will do all the work on the entities and only when it's method is done it will close the transaction. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3838553#3838553 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3838553 ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
