I got the same problem raising the same questions: Why does JBoss call CMPPersistenceManager.storeEntity() if only a finder should be invoked?
We use the default commit-option for Standard 2.x Entity Beans (commit-option B). I tried commit-option C without success. Looking through the container-configuration I noticed the "sync-on-commit-only" element set to "false" and found the following explanation in the DTD: "The sync-on-commit-only element determines the behavior of ejbStore calls on finds, selects and removes. If set to true, ejbStore will only be called on transaction commit." After I set it to "true" the exception was gone and the finder worked as expected. Axel View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975122#3975122 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3975122 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
