7 Replies Latest reply on Jul 16, 2012 12:47 PM by Jason Porter

    seam 3 remoting and conversation scope

    brvno brvnic Newbie

      Hello all, its been a while since i tried using seam 3 remoting module. I know it cannot work with jsf scopes because it operates outside of jsf lyfecycle that is fine. But i am uncertain about why is it not working with conversation scope.

       

      I have very simple project which shows this, i will attach it with this post.

       

      Basically i always get

       

       

      An exception has occurred while executing a remote request: org.jboss.weld.context.ContextNotActiveException:WELD-001303 No active contexts for scope type javax.enterprise.context.ConversationScoped

       

      Although conversation is active.

       

      i got

      <script type="text/javascript" src="seam/resource/remoting/resource/remote.js"></script>

      <script type="text/javascript" src="seam/resource/remoting/interface.js?moja.zeza.HelloWorld"></script>

       

      and my script is

       

       

      function push(){

                  Seam.context.setConversationId(#{helloWorld.conversation.id});

                  var bean = Seam.createBean("helloWorld");

                  bean.prcuknuo(function(){alert('oleeee')});

              }

       

      And every time i get that exception informing me that no conversation is active, which is not true. Inspecting the Seam.context i can see that conversationId is set to the correct value.

       

      Im guessing that the problem is that

       

       

      AbstractRequestHandler isat fault because it always associates request with NoopSeamConversationContext