-
1. Re: Pageflow & 3rd Party Site
igx89 Nov 30, 2007 1:05 PM (in response to chane)Something like the following might work:
yoursite/checkout_page
->
yoursite/paypal_payment_page
-> (using JavaScript or META redirect)
paypal.com
-> (using GET or POST with the conversation ID; not sure which would work better)
yoursite/paypal_payment_page
->
yoursite/checkout_complete_page -
2. Re: Pageflow & 3rd Party Site
pmuir Dec 1, 2007 6:32 PM (in response to chane)Keep hold of the conversation id, and you should be ok - just step back to the correct view of the pageflow and with the correct cid parameter. Let us know if this works - interesting problem :)
-
3. Re: Pageflow & 3rd Party Site
chane Dec 5, 2007 11:03 PM (in response to chane)I had the 3rd party site redirect call a stateless method. In that method I reattached the conversation from a variable included in the redirect request:
Manager.instance().restoreConversation()
After I reinstated the conversation, the Pageflow.instance() was null. Did I do something wrong.
Anyway, I restarted the pageflow and then repositioned to the node I wanted and everything worked fine.
Just curios if there was a better way to do this.
Chris.... -
4. Re: Pageflow & 3rd Party Site
pmuir Dec 6, 2007 6:09 PM (in response to chane)I'm surprised, I think the pageflow scope state should have been maintained. But its hard to know why its not without seeing the application.
If it works, then great :) -
5. Re: Pageflow & 3rd Party Site
chane Dec 6, 2007 9:56 PM (in response to chane)"pete.muir@jboss.org" wrote:
I'm surprised, I think the pageflow scope state should have been maintained. But its hard to know why its not without seeing the application.
I also thought the pageflow scope should have been in the conversation. I couldn't figure out what was causing it to not be there. I am using Seam 1.2.0 patch 1 - so maybe something there...
Since I found a workaround quickly I haven't looked deeper into the Seam code to figure out why the pageflow scope is not there. Maybe I'll get a chance when I upgrade to Seam 2.x - I have a comment in the code to look at it again.
Thanks for the suggestion on passing the conversation id around.
Chris....