I have some processing invoked from flow that's not OK to just abandon if the user abandons their session. In particular, this processing logic "reserves" some resources in the database.
BAD BAD BAD!! Don't!!
A continuation should not even keep a component reference across a suspend!
...any other way of approaching that logic? What is it?
In the case of "success", the resources will remain permanently associated with a persistent object, but in the case of "failure" or "abandoned interaction", the resources must be released.Is there any way to register a listener or something so that if a continuation is abandoned, I can release what needs to be released?
Something like that *could* be implemented but endorses a bad design. So -1 on that. cheers -- Torsten
PGP.sig
Description: This is a digitally signed message part
