OK, the exception goes away when I add an aribitrary conversation Id to the SOAP headers.
But it seems kind of counter intuitive to have a conversation id in the soap request even
for the login service. Isn;t the conversation supposed to be generated and managed by
seam? Or am I missing the point completely?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073174#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...