I am having an odd experience with updating an already persisted object. What I wanted to do was to query for an object, modify attributes (outside of the begin/end transaction) and then re-save it (i.e. update). The behavior I see is that the update silently fails.
I am able to create objects and save them, query for saved objects and update saved objects by first querying and then modifying them within the same transaction (as in UCEditProduct), so I don't believe this is a fundamental configuration issue. I am using a SessionBean to find the object, modifying it on the client side and then passing it back to the EJB server for updating. I've been able to reproduce this behavior with a very simple test case, attached. What is the correct procedure for modifying objects outside of a transaction and then saving the updates with ODMG? Joe
UpdateTest.java
Description: Binary data
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
