Why don't you just replace the message in messages.properties. IIRC, it is called 'NoConversation'.
That's a possibility I guess.
Here's a sample from wiki project's messages_en.properties:
org.jboss.seam.NoConversation=The workspace ended, timed out or was processing another request.
The only problem is what about the
processing another requestpart? I believe this has to do with AJAX calls being serialized to Seam components:
<core:manager conversation-timeout="120000" concurrent-request-timeout="500" conversation-id-parameter="cid"/>
I'm referring to the concurrent-request-timeout...
from ref doc:
Seam serializes processing of concurrent requests that take place in the same long-running
conversation context, in the same process.
If I implement your suggestion, I lose that part of the message...
What exactly are you trying to achieve? There are quite a few events, you can observe those
and show messages, but you cannot change when they are raised, unless you override core Seam
components (Manager, etc.).
Cf. Manager.java, Pages.java
org.jboss.seam.conversationTimeout org.jboss.seam.conversationDestroyed org.jboss.seam.beginConversation org.jboss.seam.endConversation org.jboss.seam.noConversation