From the same document:
The conversation context is active during any JSF request. Most conversations are destroyed at the end of the request. If a conversation should contain a state for several requests, it should be clearly moving towards a long conversation.
If the conversation is temporary (never progressed to a long action), its life cycle is associated with the request.
... Assuming the answer to the first question is yes ...
This is a no :)
... can you provide a precedent when a lengthy conversation is required? ...
All tasks ("units of work") that span more than one request.
Hope this is clear now, feel free to ask additional questions.
source share