[
https://jira.jboss.org/jira/browse/JBSEAM-3557?page=com.atlassian.jira.pl...
]
koen handekyn commented on JBSEAM-3557:
---------------------------------------
i discoverred the rationale behind this
Any <s:link> or <s:button> transparently includes the request parameter. The
value of the parameter is determined by evaluating the value binding during the render
phase (when the <s:link> is rendered).
HOWEVER
i would still propose a totally "stateless" s:link equivalent than, i defined
one as follows using facelets ( as a temp patch)
<h:outputLink id="#{id}"
value="#{facesContext.externalContext.requestContextPath}#{fn:replace(view,'xhtml','seam')}">
<h:outputText value="#{value}"/>
</h:outputLink>
s:link to page that has <param> creates referred seam component
and performs set
---------------------------------------------------------------------------------
Key: JBSEAM-3557
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3557
Project: Seam
Issue Type: Bug
Affects Versions: 2.0.2.GA
Environment: independent
Reporter: koen handekyn
Priority: Minor
let's say you have a page form1.xhtml with a form1.page.xml that contains a param
instruction that sets a page param on a seam object #{someseamobject.someproperty}.
let's say you have a main page with an s:link to form1.xhtml.
when opening the main page that does NOT have ANY reference to
"someseamobejct" however, seam instantiates "someseamobject', seamingly
because there is an s:link to a page that has a param instruction on
"someseamobject'.
most of the times this just wastes resources or at best instantiates components to
early.
FIX: DO NOT USE S:LINK but fall back to h:outputLink (which has other drawbacks)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira