The one nice thing about using a parameter is that you have to opt-in to
the conversation; in fact without it, you couldn't have multiple
conversations going on under the same form bean. So Michael I wouldn't
throwaway this solution; Antonio makes a good point and I think that
idea is *very essential* to have. This will allow multiple windows etc;
nothing stops you from spawning one conversation from another, just like
our threads sometimes. haha :-)
Paul
Antonio Petrelli wrote:
Michael Jouravlev ha scritto:
I was thinking on using Stripes approach, but I don't like to mange
URLs.
I read what you mean about mangling URLs. As maybe you have noticed,
Scopes (with "click" scope), instead of using a URL parameter uses a
"cookie parameter" (correct the term, I think it is wrong) just like the
"jsessionid" produced when cookies are not enabled. For example:
http://localhost:8080/webapp/action.do?param=value;click=CLICK_ID
Anyway Scopes produces it only when redirecting (using a filter). Are
there any other cases where you lose request-scoped objects during a
"rollover"? Maybe I am missing something.
Ciao
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]