I found out a more simple way for my issue: The application-wide transaction (for the lazy loading) now loads all Objects in read-only-mode. In my object-manipulating-methods I start another transaction and reload the objects readable.
I hope this is a reasonably good solution. Thanks for your help so far! Tatjana >>-----Urspr�ngliche Nachricht----- >>Von: Bruce Snyder [mailto:[EMAIL PROTECTED] >>Gesendet: Freitag, 13. Juni 2003 21:27 >>An: [EMAIL PROTECTED] >>Betreff: Re: [castor-dev] LockNotGrantedException persist.writeTimeout >> >>This one time, at band camp, Tatjana Manych said: >> >>TM>"scope" was a really good hint!!! >>TM>I solved my problem now... thanks a lot! >>TM> >>TM>The problem was, that I had the object I wanted to delete in two >>TM>transactions at the same time. I now closed one of those and it works. >>TM> >>TM>Isn`t it possible to have one object in two transactions? Is there any >>TM>way? >>TM>It would be really usefull for me, if this could be realized: I want to >>TM>have one transaction over the whole application for the lazy loading >>and >>TM>another for my delete-, update- and insert-functions. >>TM>Can I use the "shared"-Field in org.exolab.castor.jdo.Database >>TM>therefore? >> >>This type of functionality would require Castor to handle nested >>transactions. I've never even considered implementing this simply >>because this type of functionality should be using a real transaction >>manager. The likes of which can be found in Tyrex (http://tyrex.sf.net/) >>or any J2EE application server. >> >>Bruce >>-- >>perl -e 'print unpack("u30","<0G)[EMAIL PROTECTED]&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 ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
