2 Replies Latest reply on Nov 2, 2010 4:38 AM by baz

    @Conversational problem

    baz
    baz Oct 28, 2010 3:14 AM

      Hello,

      We have problems to go to pages which are backed by beans with @conversational annotation. See here

      http://community.jboss.org/message/568746#568746

       

      I have extended thecode to do an user search:

       

      {code}
      assertEquals("/fong/person/person_search.xhtml", server.getCurrentViewID());
       
            client.setValue("userId", "person");
            client.click("searchUser");
      {code}

       

      The backing bean code is executed but there is a failure to rerender the page with the results.

      The error Message states that #{PersonSearchBean.Maxresults} could not be accessed.

      If we remove the @Conversational than the test runs fine.

       

      After navigation to  person_search.xhtml the PersonSearchBean must be instantiated and there must be an conversation.

      Here is the code for the searchUser Button:

       

      {code}
      <h:commandButton id="searchUser" action="#{personSearchBean.search}" value="#{messages.global_search}" 
       styleClass="standardButton">
              <s:defaultAction id="defaultSearchUser"/>
              </h:commandButton>
      {code}

      Any ideas?

      Ciao,

      Carsten

      • 4497 Views
      • Tags:
        • 1. Re: @Conversational problem
          blabno
          blabno Nov 2, 2010 4:11 AM (in response to baz)

          Please show us pages.xml or x.page.xml of page from which you navigate to person_search.xhtml and person_search.page.xml.

          Don't you get any stacktrace in server logs?

            • Actions
          • 2. Re: @Conversational problem
            baz
            baz Nov 2, 2010 4:38 AM (in response to blabno)

            Hello,

            here are both page.xml

            start.page.xml:

            {code}
            <description>Start</description>
            <action execute="#{navigationManager.selectNavigationId(1)}" on-postback="false"/>
            {code}

             

            person_search.page,xml

            {code}
            <description>Person suchen</description>

                <param name="cleanConversation"/>
                <action execute="#{navigationManager.cleanConversations}" if="#{cleanConversation.equals('true')}" on-postback="false"/>
                    <restrict>
                        #{rightsResolver.hasRight("navigation_user_search", "access", "true") or rightsResolver.hasRight("navigation_management_search_user", "access", "true")}
                    </restrict>
            {code}

             

            What we have discoverd is this:

            When we try our usecase with a browser we get  four/five conversations

            When we use the testscript, then more than 12 conversations are created. It seems that conversation propagation does not work with our pages:-(

             

            Ciao,

            Carsten

              • Actions