if u are going from page A - page B using a commandlink then u the <f:param>
<h:commandLink immediate="true" action=""> <f:param name="username" value="#{ summary.id}"/>
<h:outputText value="#{summary.id}"/>
</h:commandLink>
While this solution is technically feasible, it has some problems, too:
* It restricts you to using hyperlinks instead of submit buttons.
* It requires the view tier to be aware of implementation details that
properly belong in the model and controller tiers, so it makes your
application more fragile when you change things later.
I'm somewhat of a radical on this topic, but I believe that developers of web *applications* should forget that URLs even exist, and focus on passing information on the server side (via request or session scoped attributes, as appropriate). Then, if you really really really find you need to get the view tier involved, use a hidden variable instead of explicit query string parameters. That way you can still leverage the standard form processing capabilities JSF provides.
Craig McClanahan
