This one time, at band camp, Klaasjan Brand said: KB>My classes are: KB>Mutation - contains a list of "Value" objects KB>I've got a few different "Value" types ( UserValue, ProductValue) which KB>inherit from the base class Value. KB>When I change a Mutation object in a transaction I only change the base KB>fields of the Value objects so it's not a problem the "specialized" KB>fields are not available. KB>The problem occurs when I first run a transaction which changes a KB>UserValue object followed by a transaction changing a Mutation object KB>which contains the same UserValue object. The Mutation contains only KB>Value objects, but Castor seems to remember it was a UserValue and tries KB>to get/set fields from the UserValue class too, resulting in a KB>transaction rollback _and_ and exception because the rollback tries to KB>change the UserValue fields too... KB>When I restart the application between those 2 transactions everything KB>runs fine, so I figured it was a caching issue. Disabling the caching by KB>setting cache-type="none" in the mapping.xml circumvents the problem. KB>I've tried to step through the Castor sources, but didn't find the KB>problem yet. Maybe anyone can give me a hint, or better, help find the KB>problem ;)
Klaasjan, This could, in fact, be a bug. If you're interested to work on it, I would suggest that you start by writing a test case to prove the bug using the Castor JDO test framework (http://castor.exolab.org/test-framework.html). This allows someone to better understand the situations under which the bug can be reproduced so that they can start to debug the code base a create a patch. Bruce -- perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");' ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
