]
Christian Bauer commented on JBSEAM-691:
----------------------------------------
Or simply do not append the page parameter if the value binding resolves to
'null'. I don't think ?param=null is useful anyway, so I might as well null
out the value before Render Response in some cases.
Ability to turn off page parameter appending for s:link
-------------------------------------------------------
Key: JBSEAM-691
URL:
http://jira.jboss.com/jira/browse/JBSEAM-691
Project: JBoss Seam
Issue Type: Feature Request
Components: JSF
Reporter: Christian Bauer
Priority: Minor
You have basically two choices how you can transport state in a RESTful way between
pages:
A. Use <s:link>, append the parameters manually, and pull the state on the target
pages' backing bean with @RequestParameter
B. Use <s:link>, and let Seam automatically append the parameters that the target
page requires (pages.xml parameters), set the values on the backing bean that way
Option A seems to be a good overall strategy if you rarely have to pass parameters
around. Option B is the "always pass parameters around" option.
In practice, you need a mixed strategy frequently. You might go for option B because it
is so convenient, but disabling the parameters when _not_ needed (because the target page
treats them conditionally, for example) requires customized <s:link> declarations,
like:
<s:link action="foo"><f:param
name="aParamIDoNotWantToPropagate" value=""/></s:link>
Effectively, page parameters currently guarantee that every link to that page contains
the specified parameters. I want to sometimes disable this guarantee, e.g. with <s:link
parameters="none"/>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: