Take the 2-minute tour ×

My problem is that when I for example do this

<h:outputLink value="changeinfo.jsf">
                Change name
                <f:param name="change" value="name"/>

then the requested url is


My url pattern for the faces servlet look like this


Now on the changeinfo page

<f:verbatim rendered="#{'bean.param'} == 'name'"> 
<h:form id="form1"> 

Then on the generated html page I only see the word NAME and not the form. Why is this?

share|improve this question
It should work just fine. The query string won't be tested at all on url pattern match. Your problem lies somewhere else. What JSF impl/version? What webserver impl/version? Have you double, no, triplechecked the URL? –  BalusC Jul 30 '10 at 13:58
that url IS matched by that pattern. So you have a problem elsewhere. Check the logs. –  Bozho Jul 30 '10 at 13:59
You may want to re-elaborate what you meant with "rendered". The ambiguity of the problem might be in there. –  BalusC Jul 30 '10 at 14:05
It is JSF 2.0 and glassfish v3. Right now I am trying to make a navigation case as in link in volothamp's answer. –  AnAmuser Jul 30 '10 at 14:41
And it does not work either. –  AnAmuser Jul 30 '10 at 14:42

2 Answers 2

up vote 2 down vote accepted

You can't put JSF components inside a f:verbatim, only plain vanilla HTML. Use h:panelGroup instead.

Also, get rid of those quotes around the bean property identifier in EL. It would otherwise be treated as a plain vanilla string. You should also put the string comparison inside the EL expression.


<h:panelGroup rendered="#{bean.param == 'name'}">

As an extra hint: you can just access request parameters by #{param}. If you don't need it further in the managed bean, then you can also just do so:

<h:panelGroup rendered="#{param.change == 'name'}">
share|improve this answer
Darn you BalusC! Always answering JSF questions before I get to! ;P –  Drew Jul 30 '10 at 21:54

Have you seen this: How to create a GET request with parameters, using JSF and navigation-rules?

The problem is not the extension, but that JSF doesn't support this approach out of the box. If you have to code the McDowell solution or change web framework using for example Seam.

BTW, JSF 2 will support this style of navigation. Take a look at: fluent-navigation-jsf-2

share|improve this answer

Your Answer


