Hi,

I used to put some logic in the stored method which did castor
cache-refreshes remote and some other logic. It seemed however that the
locks were not released on the entities when "stored" was called so the
application just hung. Is that the right conclusion?

It is very important for me to be able to decide if the entity is really
going to be commited or not - is that absolutely decidable in
created/updated? Is the transaction absolutely over when those calls are
made so I don't get a lock problem again?

Regards
Mattias Bogeblad

_______________________________________________________________ 
Mattias Bogeblad  |  PH: +46 31 761 09 03 |  MOB: +46 702 80 05 05 
SPRAWL SOLUTIONS AB
Drottningatan 5
403 14 G�TEBORG
_______________________________________________________________ 
 

-----Ursprungligt meddelande-----
Fr�n: Bruce Snyder [mailto:[EMAIL PROTECTED] 
Skickat: den 2 september 2004 20:03
Till: [EMAIL PROTECTED]
�mne: Re: [castor-dev] CallbackInterceptor release method


Mattias Bogeblad wrote:

> Does anyone know the CallbackInterceptor good. I�m having problems 
> intercepting which objects will in the end be actually committed to
the 
> database from the released-method. The commit-flag does not seem to 
> reflect the actual state. The storing-method is better but that one is

> not good enough for me � I need a method which invokes after the
actual 
> commit as I want to start processes interfering with the locks castor
has.

Matthias,

Will the created() and updated() callback methods work for you or do you

need something more?

Bruce
-- 
perl -e 'print 
unpack("u30","<0G)[EMAIL PROTECTED]&5R\\"F9E<G)E=\\$\\!F<FEI+F-O;0\\`\\`");'

The Castor Project
http://www.castor.org/

Apache Geronimo
http://incubator.apache.org/projects/geronimo.html



----------------------------------------------------------- 
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

Reply via email to