Hello Fabrizio,
I am a bit of a newbie with seam but I have learned to watch for the
"conversationId=xxx" on the browser status and on links. Seam will not be able
to "find" the long-running conversation if the the ID is missing, & so will
create a new converasation. If you look at the link gen
After some experiments I realized that:
1) If I start the Test page from the browser with
localhost:8080/application/Test.seam and I refresh the page a new conversation
is started. This is true if and only if I have a call to the TestBeam (ex
or the dataTable)
If I have not a call to the TestB
Norman,
I have shown only a small part of my code.
I have information that should be shared between different conversation so I
decided to put the TestManagerBean into the session.
Anyway, I have changed the scope from SESSION to CONVERSATION but the behaviour
is the same.
Each time I refresh
Taking a step back, why are you trying to start a conversation with a session
scoped component?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998305#3998305
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3998305
_
