[
https://issues.jboss.org/browse/FORGE-1228?page=com.atlassian.jira.plugin...
]
Lincoln Baxter III commented on FORGE-1228:
-------------------------------------------
I think it's fine to make this change. I agree that the default timeout might be a bit
short. I'm wondering, though, if there is a more global setting that can be used
instead of setting the value of each conversation instance directly.
increase conversation timeout to 30 minutes
-------------------------------------------
Key: FORGE-1228
URL:
https://issues.jboss.org/browse/FORGE-1228
Project: Forge
Issue Type: Enhancement
Components: Scaffold
Affects Versions: 1.4.1.Final
Reporter: Gerry Matte
Priority: Minor
Fix For: 1.x Future, 2.x Future
The scaffold generated entity DAO beans contain two conversation.begin() commands [in the
create() and retrieve() methods]
After each conversation.begin() please insert:
this.conversation.setTimeout(1800000);
which will extend the conversation timeout from the default ten minutes to thirty minutes
(same as the session timeout)
For me, complex data entry screens often have their conversation expire during the period
that a user composes and keys their data. Very frustrating !
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira