This one time, at band camp, David Colwell said:
DC>I'm using "shared" locking. I tried "exclusive" locking, and get an
DC>exception while attempting to load the object initially:
DC>
DC>detailMessage= "Lock conflict: attempt to load object of type
DC>com.xyz.Account with identity 123001 in two different"
DC>
DC>I'm not sure why this would occur as I have only the one JUnit process
DC>running a single test. Is there a way of extracting more Castor information
DC>at runtime? Any other thoughts how to track this down?
Please post your mapping descriptor and the relevant client code. If all
you're doing is running a simple, self-contained JUnit test, the only
thing that I can think of that would cause this is the order in which
the tests are executed by JUnit.
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
