seam 3 remoting and conversation scope

[brvuga]

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

[brvuga]

Now i see that on the first reqeust i always get this warrning in my logs:

org.jboss.seam.conversation.spi.SeamConversationContextFactory create

WARNING: No matching SeamConversationContext for store type interface javax.servlet.http.HttpServletRequest, using NOOP instance!

Does that mean that remoting with conversations cannot work on tomcat 7, or am i using it in a wrong way?

[lightguard]

It uses the session, so if you're not keeping a session around via a cookie or query param you're probably out of luck and would need to create your own scope.

[brvuga]

Hello, thanks for your answer.

I am keeping a session. I've got the little test app attached to the original post. The test app is just a weld archetype for servlet containers which i got from the seam site, with updated dependancies and added seam remoting and stuff.

If my bean in that app is either request scoped or session scoped everything works fine. But ConversationScoped is not working because of the NoopInstance thingie.

I repeat its not working on Tomcat7. Maybe theres an issue with tomcat7.

[lightguard]

Certainly possible. Honestly, if you're using tomcat, why not look into TomEE?

[brvuga]

Does this mean that servlet containers are not supported by seam 3 any more?

[brvuga]

I will interpret the silence of seam guys as YES, and I think most of the readers will agree with me.

[lightguard]

Seam 3 has always targeted Java EE 6. If you can get things working in a servlet container, great, but it hasn't been anything we put major resources into.