4 Replies Latest reply on Dec 17, 2007 3:19 PM by damianharvey

    a4j:include and seam navigation

    maumau

      Hi,

      Did someone succed using "a4j:include" with the seam
      navigation logic defined in pages.xml ?

      My goal is to create a nested conversation...


      Sincerely

      Malte

        • 1. Re: a4j:include and seam navigation

          I have troubles using a4j:include and seam navigation in pages.xml.

          If i define logic in faces-config.xml:

          <navigation-rule>
           <from-view-id>/test/firstTest.jspx</from-view-id>
           <navigation-case>
           <from-outcome>next</from-outcome>
           <to-view-id>/test/secondTest.jspx</to-view-id>
           </navigation-case>
           </navigation-rule>
          

          everything is ok - navigation occurs only inside a4j:include-d page, but if i use pages.xml:
           <page view-id="/test/firstTest.jspx">
           <navigation>
           <rule if-outcome="next">
           <redirect view-id="/test/secondTest.jspx" />
           </rule>
           </navigation>
           </page>
          

          navigates the whole page.

          /test/firstTest.jspx included into parent page:
          <a4j:include viewId="/test/firstTest.jspx"/>

          JBoss Seam version : 2.0
          RichFaces : 3.1.2

          Is this Seam or RichFaces problem?

          • 2. Re: a4j:include and seam navigation
            pmuir

            A mixture :) Please file an issue in JIRA, we'll try to take a look...

            • 3. Re: a4j:include and seam navigation

              I've created JIRA bug about this problem.

              http://jira.jboss.org/jira/browse/JBSEAM-2254

              • 4. Re: a4j:include and seam navigation
                damianharvey

                Had a go with these today. The trick (as mentioned in the JIRA) is to use render rather than redirect in the pages.xml. Also worth noting is to define the page rule for the included pages not on the page doing the including. Maybe obvious to most, but I was puzzled for a while as it's the opposite to a ui:include.

                Cheers,

                Damian.