-
1. Re: Login Redirection not propagating GET parameters
milli Aug 9, 2007 12:44 PM (in response to zdaler)I'm having the same problem too and waiting for a response
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=115645 -
2. Re: Login Redirection not propagating GET parameters
zdaler Aug 10, 2007 5:18 AM (in response to zdaler)maybe we will have to post an issue in JIRA ...
-
3. Re: Login Redirection not propagating GET parameters
milli Aug 10, 2007 11:53 AM (in response to zdaler)Anyone?
-
4. Re: Login Redirection not propagating GET parameters
milli Aug 10, 2007 12:05 PM (in response to zdaler)I saw Gavin's response in an earlier posting with the similar problem http://www.jboss.com/index.html?module=bb&op=viewtopic&t=101357&start=20 that you need to define them as page parameters.
I have it as @RequestParameter in the backing bean. Isn't it already defined as a page parameter? Or do I need to do something else?
Please help! -
6. Re: Login Redirection not propagating GET parameters
milli Aug 10, 2007 3:10 PM (in response to zdaler)Thanks Pete. Meanwhile I tried to debug and found out it works only if you define it in page.xml and not when you use the annotation @RequestParameter.
Shouldn't passing parmeters to the page either by defining in pages.xml or by annotation @RequestParameter have the same behaviour? -
7. Re: Login Redirection not propagating GET parameters
pmuir Aug 10, 2007 3:13 PM (in response to zdaler)No. They are not semantically identical. @RequestParameter is simply for injecting a request parameter, page parameters have a deeper effect on your app (parameter propagation, setting values on your model, application of converters).
-
8. Re: Login Redirection not propagating GET parameters
milli Aug 10, 2007 7:34 PM (in response to zdaler)"pete.muir@jboss.org" wrote:
No. They are not semantically identical. @RequestParameter is simply for injecting a request parameter, page parameters have a deeper effect on your app (parameter propagation, setting values on your model, application of converters).
I understand with page definition you can do more than a simple @RequestParameter injection.
Let's forget about propagating parameters values for a while. But when it comes to just passing GET parameters(to the backing bean component) shouldn't they be having the same behaviour?
Here is what I found out.
When you have the parameter defined in pages.xml, here is the flow of the backing bean component:
* Seam calls @Create method first
* It then calls setters on the parameters to initialize the values
With @RequestParameter, the behaviour is
* Seam injects parameter values first (No need to have setters)
* It then calls the @Create method
Is this the intended behaviour? May be there was a reason to design this way which I don't get it. -
9. Re: Login Redirection not propagating GET parameters
pmuir Aug 11, 2007 6:28 AM (in response to zdaler)"milli" wrote:
Let's forget about propagating parameters values for a while. But when it comes to just passing GET parameters(to the backing bean component) shouldn't they be having the same behaviour?
Here is what I found out.
When you have the parameter defined in pages.xml, here is the flow of the backing bean component:
* Seam calls @Create method first
* It then calls setters on the parameters to initialize the values
With @RequestParameter, the behaviour is
* Seam injects parameter values first (No need to have setters)
* It then calls the @Create method
The behaviour you describe is consistent through Seam. @RequestParameter does injection (which of course occurs before @Create but after the constructor), page parameters set model attributes (which occurs after the constructor and @Create). Spend some time understanding what injection is and what page parameters are. -
10. Re: Login Redirection not propagating GET parameters
milli Aug 11, 2007 4:03 PM (in response to zdaler)Thanks for your reponse and I get it. I appreciate you guys taking time in responding to everybody's issues promptly and keeping the community active.
I usually refer to Seam book and Reference guide but the difference between page parameter and @RequestParameter llife cycle was not mentioned.