9.4. Workspace Timeout

We discussed the conversation-timeout previously, but now we will revisit the conversation timeout to see how it relates to user experience. At first glance, most developers relate conversation-timeout to session timeout where any conversation will simply time out after the configured conversation timeout period (see Section 8.2.3). As you will quickly notice during testing, this is not the case. The conversation timeout is best explained through interaction with a Seam application. Try the following configuration in the components.xml of the Seam Hotel Booking example:

... ...

<core:manager conversation-timeout="60000" />

... ...