Same story as issue 698. I noticed this during a presentation, and haven&#39;t remembered to submit until now. I should have caught this before final draft.<br><br>When using implicit navigation, you can pass flags through the query string that<br>
alter the behavior of the navigation. The first is a redirect flag, the second<br>is a hint to include view parameters in the outgoing query string.<br><br>- faces-redirect<br>- includeViewParams<br><br>As you can see, there are two problems with the includeViewParams flag. First,<br>
it uses camel case instead of hyphen delimiters between words and it is not<br>prefixed with faces-.<br><br>When this feature was being discussed, there was a concern that the hints would<br>collide with query string parameters used by the application. As a result, a<br>
prefix was added to the redirect hint, making it faces-redirect. However,<br>includeViewParams was not updated.<br><br>Here&#39;s the following change that needs to happen in the spec:<br><br>includeViewParams ==&gt; faces-include-view-params<br>
<br>And in use:<br><br>/entry?faces-redirect=true&amp;faces-include-view-params=true<br><br>In the long run, we need to find a cleaner (perhaps type-safe) way of indicating<br>an implicit navigation. Using the query string really isn&#39;t great. Perhaps under<br>
the covers the implicit navigation is communicated this way, but we provide a<br>Java API that generates this in toString()<br><br>return new Navigation(&quot;entry&quot;, true, true);<br><br>-Dan<br clear="all"><br>-- <br>
Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>