As ever, you need to post code and stack traces and a clear flow that we are taking through your app.
Pete, I described an idea I was prototyping and then dropped due to this exception some time ago. So I have no adequate code to illustrate this. I hoped that this flow is a generic problem, please bear with me:
1. start LR conversation
2. go through a multipage wizard
3. present confirmation page
OKaction is executed we invoke a checkAndFlushAndRedirect() method in a
This method either:
ERRORoutcome, resulting in JPDL redirection to step 3.
4b. or send to user's browser a HttpServletResponse.sendRedirect() to the payment service site URL
5. After processing, payment service site GET-redirects to one of the two URLs in Seam application: urlOK for OK, urlREJECT for REJECT.
6. both urlOK and urlERROR resumes the conversation (basing on its ID?) and allow finishing conversation or fixing the data
in the context of this conversation.
But step 4b. was causing a
pageflow is not at page nodeexception because I was apparently interfering with JPDL flow processing. So doing some kind of suspend/leave on this JPDL flow
could help me to deal with this.
Is it possible somehow? Or should I do it in another way?
Hmm. So you get an exception when you send the redirect? Not sure without a stack trace.
This should work - but you will have to restore the pageflow manually when you return. Might be nice to make it easy for you to do this in Seam. File a feature request.