FR: customizable per-conversation timeout value

[przemjaskier]

What about providing a property for @Begin that would allow to specify what is a timeout of a given conversation? Depending on a context, some conversation should be valid for a long time, some not...

[pmuir]

Put a feature request in JIRA - and see what happens :)

[gavin.king]

You can put interceptors in ejb-jar.xml, if they are session bean components.

[przemjaskier]

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 page still shows this conversation's timeout value as equall to the one set in Manager component.

It's because calling conversation.setTimeout() has no effect, or am I doing something wrong handling conversations this way?

TIA

[gavin.king]

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.