-
1. Re: Still confuse on usage of page param, help please!
shane.bryzak Jan 21, 2008 7:47 PM (in response to gus888)The page params are actually needed, the reason it was still working when you commented them out is because I'd originally used @RequestParameter params and forgot to remove them. I've fixed up the example in CVS so it should make more sense now.
-
2. Re: Still confuse on usage of page param, help please!
gus888 Jan 22, 2008 5:36 PM (in response to gus888)Thanks, Shane.
So, based on my understanding on page parameter, when I click on <s:link view="/comment.seam">, the link's f:param will pass "#{selectedMember.memberName}" to "name", and redirect to /comment.xhml page, then page param will get the "name" value and pass it to "#{selectedMember.memberName}" in bean. Is it correct? Thank for any guidance. -
3. Re: Still confuse on usage of page param, help please!
gus888 Jan 23, 2008 12:59 PM (in response to gus888)Anybody can confirm my understanding on page parameter is correct or not? Thank you.
So, based on my understanding on page parameter, when I click on <s:link view="/comment.seam">, the link's f:param will pass "#{selectedMember.memberName}" to "name", and redirect to /comment.xhml page, then page param will get the "name" value and pass it to "#{selectedMember.memberName}" in bean. Is it correct? Thank for any guidance.
-
4. Re: Still confuse on usage of page param, help please!
pmuir Jan 23, 2008 1:02 PM (in response to gus888)No, when the page is renderered, the EL will be evaluated. When the link is clicked, the params are sent as GET parameters, and then correct.