Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I know how to use @ConversationScoped in a wizard consisting of multiple pages. I was wondering, though, what happens when users abort the wizard by navigating somewhere completely unrelated? How can the container figure out the conversation has ended when the conversation scope doesn’t seem to be tied to any JSF view states?
If the conversation scope is indeed leaky, what are some good strategies for mitigating this problem?
Conversations time out if not used for a certain amount of time.
The default timeout value set by the container can be modified on a single conversation instance by mean of this API: Conversation.setTimeout()