Why can I hold on to a cmr-field (Container Managed Relationship) collection and use it after the transaction commits?
A. This is prohibited by the EJB 2.0 specification. The reason for disallowing this is that the DBMS data backing a cmr-field collection can change in unpredictable ways once your transaction commits. Tracking these changes is difficult and can result in the contents of the cmr-field collection changing when the application doesn’t expect it. The bottom line is that developers must retrieve and access cmr-field collections within a single transaction.
Related Questions
- How do I set the Transaction Isolation level for Container Managed Transactions in OC4J? Which isolation levels are supported?
- How many pounds of portable rechargeable batteries and cell phones will a collection container hold?
- Do you believe that women are magical beings that hold the key to happiness?
