3 Replies Latest reply on Oct 17, 2007 3:30 PM by Sebastián Fiorentini

    Richfaces + Seam + JPDL problem

    Sebastián Fiorentini Newbie

      This is the scenario. I have a page with a richfaces commandbutton which haves in the action attribute a pageflow transition (defined in jpdl) that stays in the same page (there is a condition that for testing purposes always return false, which means to stay in the page). The expected behavior is to re render the faces messages. In any case, the page gets fully re rendered, in other words, no ajax re render. But If I put in the action parameter a method binding, that returns null (or a void method) the page doesn't get re rendered and works as expected.
      I am doing something wrong? I think that something with the PhaseListeners or something else is working wrong.

      Any help will be appreciated.
      Regards
      Sebastian

        • 1. Re: Richfaces + Seam + JPDL problem
          Sebastián Fiorentini Newbie

          Another thing that doesn't work is the rich:include componente. If you use faces-config (uggg) navigation rules, it works as expected, but if you use jpdl navigation simply it doesn't work.

          Regards
          Sebastian

          • 2. Re: Richfaces + Seam + JPDL problem
            Alexander Smirnov Master

            First - jpdl navigation in Seam, in case of the no transision to other state, really perform JSF navigation to same viewId. ajax4jsf framework detect it as real navigation, and switch rendering to the non-ajax. This is a difference with JSF navigation case, where is "null" action mean "continue to processing current page".
            Second - really, this is difference in the navigation processing in the Seam and a4j:include. This is a known issue, don't solved yet.

            • 3. Re: Richfaces + Seam + JPDL problem
              Sebastián Fiorentini Newbie

               

              "alexsmirnov" wrote:
              First - jpdl navigation in Seam, in case of the no transision to other state, really perform JSF navigation to same viewId. ajax4jsf framework detect it as real navigation, and switch rendering to the non-ajax. This is a difference with JSF navigation case, where is "null" action mean "continue to processing current page".
              Second - really, this is difference in the navigation processing in the Seam and a4j:include. This is a known issue, don't solved yet.


              Thanks. I'll look into seam forums to see how to issue a "null" transition within jpdl pageflow.