On Thursday 09 August 2001 15:18, Thomas Yip wrote:
> Can you give us a line number where the exception is eaten?
>
>
> Thomas
>
cvs diff src/main/org/exolab/castor/persist/ClassMolder.java
Index: src/main/org/exolab/castor/persist/ClassMolder.java
===================================================================
RCS file:
/cvs/castor/castor/src/main/org/exolab/castor/persist/ClassMolder.java,v
retrieving revision 1.60
diff -r1.60 ClassMolder.java
742,746c742
< try {
< temp = tx.load( fieldEngine, fieldClassMolder,
fields[i], null, suggestedAccessMode );
< } catch (Exception ex) {
< temp = null;
< }
---
> temp = tx.load( fieldEngine, fieldClassMolder,
fields[i],
null, suggestedAccessMode );
> -----Original Message-----
> From: Steve Vaughan [mailto:[EMAIL PROTECTED]]
>
> >Sent: Thursday, August 09, 2001 9:56 AM
> >To: [EMAIL PROTECTED]
> >Subject: [castor-dev] Write access and Cached Read Access Relations Bug
> >
> >I've uncovered a bug which occurs when there is an object with related
> >objects which are cached. If you attempt to load the object in a write
> >access mode (DbLocked or Exclusive), there is an exception thrown in the
> >TransactionContext class due to a "lock conflict". However, this
> > exception is caught in ClassMolder and the field is set to null without
> > reporting an exception. The object is thus loaded without any of the
> > cached relations without reporting an error. To make matters worse, when
> > the transaction is committed the relationships are lost.
> >
> >I don't know enough about the code in the TransactionContext to know how
> > to fix this, but in the mean time I would suggest that the exception be
> > propagated at the very least. This would allow users to know that an
> > exception has occurred which involves caching.
> >
> >-Steve
> >
> >_________________________________________________________
> >Do You Yahoo!?
> >Get your free @yahoo.com address at http://mail.yahoo.com
> >
> >-----------------------------------------------------------
> >If you wish to unsubscribe from this mailing, send mail to
> >[EMAIL PROTECTED] with a subject of:
> > unsubscribe castor-dev
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
