Petemuir, anonymous wrote : I don't quite get what you are after here. You want to have it so that conversations can never timeout? Then it's just SESSION scope (but admittedly isolated)... -> SESSION scope is never a good implementation unless you have a very good reason to go for, neither a very long running conversation timeout or even set it to the same time-out as the HTTP session time out. Standard is 30 minutes, or at least most of my apps. anonymous wrote : You can already achieve this effect by having a very very long conversation timeout. ->. Imagine that your application has tab and tree UI components exposed all time and setting the conversation timeout greater than the HTTP session time out or unlimited, aren't you asking for trouble? You will have a whole bunch of runaway conversations running behind the scene and waiting to be closed by the their conversation timers, assume that the user did not click on the DONE or CLOSE button to close the forms' conversations properly. anonymous wrote : Or are you after flexibility - giving different conversations different timeouts (you can currently do this programmatically, but not through xml/annotations) -> Who would you go about that? And would that manually setting be scattered all over the place, for each component that is? What we need is the ability to control the conversation time-out to rely on the HTTP session timeout or a way to disable the conversation timeout but not by means of "never timed out conversations" Just try to put a complex UI application that has a lot of business components with tree+tab interfaces and see how sufficient the application conversation stack can be. Please make sure that "the application data entry form has to be in the edit mode all the time unless the user want to close the form by clicking on the DONE, CLOSE or whatever... button to get back to the search result page". Thank you all. John View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038107#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...