Hi there,
I have a question about the implementation of @Begin. At the moment the @Begin is only done AFTER a bean method has completed it's invocation. Is there any reason why it is done like this rather than beginning the conversation before the method invocation. The only thing I could think of was if an exception occurs the conversation state would need to be rolled back.
If I do a manual Redirect.execute() in methods which have @Begin(nested = true) then the nested conversation id is not correctly propogated on the redirect as the nested conversation is not begun until after the method completes, by which point the redirect has happened.
Would it be possible to change this behaviour (this also seems more natural to me to begin the conversation before the method), or would this have too many breaking side-effects?
Cheers.
Mike.
