anonymous wrote : Seam's debug page still shows this conversation's timeout
value
Where on the debug page are you looking?
Conversation.instance().setTimeout(...) is the correct way to do it.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025298#4025298
Rep
Gavin, my target platform is pure Tomcat.
I create my conversations using Conversation.instance(),begin()/beginNested().
I spotted conversation.setTimeout() method, and thought that this will provide
such low-level control on a given coversation lifetime. But when I set this
value, Seam's debug
You can put interceptors in ejb-jar.xml, if they are session bean components.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024857#4024857
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024857
_
Put a feature request in JIRA - and see what happens :)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024841#4024841
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024841
___
