"[EMAIL PROTECTED]" wrote : somehow, to cut down the run-away conversation and to end it. Otherwise, one has to implement @Begin(join=true) so no errors occur but doing this is not healthy for an app server.
AFAIK there is nothing wrong in "health" terms with @Begin(join="true")/allowing conversations to timeout (rather than explicitly ending them) - what do you see as the issue? Of course, it may not be the best way to do it architecturally... If the tabs and tree are there for the entire user session, perhaps they should go in the session (you could consider doing any persistence work in the current conversation to avoid LIEs, but keep the state in a session)? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4027001#4027001 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4027001 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
