2 Replies Latest reply on Jun 8, 2007 3:50 PM by Gavin King

    a4j:region and conversationID

    Andrea mazant Newbie

      Hi all,
      is it possible to add the conversationID of a long running conversation inside an ajax4jsf region?
      I've a region that use EJB with scope conversation, when the region is submitted, only the data inside the region are submittetd so seam create new EJB. But I need to access to the EJB in the conversation not a new.

      I've try with

      <a4j:region renderRegionOnly="false"


      but with this way all the field in the page are submitted. It works but there is a lot of bandwidth waste.


      -mazant-

        • 1. Re: a4j:region and conversationID
          Gavin King Master

          No, its not. Seam keeps the conversation id in the UIViewRoot, so if you want to change the conversation context from a partial render, you would need to render the whole f:view (which is not really a partial render!).

          This is definitely a limitation of the current design (closely related to our limitation that there may be only one conversation per page), but I believe it's perfectly fine for almost all purposes.

          However, this should be documented, since it is not at all intuitive unless you happen to know how Seam in implemented. So please create in issue in JIRA, asking for documentation, and assign it to me. Thanks.

          • 2. Re: a4j:region and conversationID
            Gavin King Master

             

            "gavin.king@jboss.com" wrote:
            No, its not. Seam keeps the conversation id in the UIViewRoot, so if you want to change the conversation context from a partial render, you would need to render the whole f:view (which is not really a partial render!).

            This is definitely a limitation of the current design (closely related to our limitation that there may be only one conversation per page), but I believe it's perfectly fine for almost all purposes.

            However, this should be documented, since it is not at all intuitive unless you happen to know how Seam in implemented. So please create in issue in JIRA, asking for documentation, and assign it to me. Thanks.


            I just want to say that this is total crap - I spoke to Igor and Alexandr yesterday, and Ajax4JSF *always* updates the view state from UIViewRoot down.