While researching an issue using JSF 2 with Seam 2, I uncovered a pitfall with implicit navigation. In cases where frameworks assume that a formal navigation rule is required to trigger navigation, implicit navigation is now causing navigation to trigger unexpectedly. My first thought was to first check if a matching navigation case exists, except that an implicit navigation case is currently indistinguishable from a formal navigation case. Thus, I have filed an issue requesting an enhancement to add an implicit (or derived) flag to the navigation case which indicates that the navigation case is not backed by a formal rule. (Another idea/option would be to use a subclass).<br>
<br><a href="https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=736">https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=736</a><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>