[cdi-dev] [JBoss JIRA] (CDI-207) Specify @Destroyed event payload type for a timed-out conversation
[
https://issues.jboss.org/browse/CDI-207?page=com.atlassian.jira.plugin.sy...
]
Martin Kouba commented on CDI-207:
----------------------------------
Actually the conversation id is not available for transient conversations.
Pete suggested to have two variants of payload (ServletRequestEvent for transient
conversations and conversation id for long-running ones).
We should also consider adding two more events to observe long-running conversation start
and end.
The payload could be something like (and may be reused for timeout @Destroyed):
{code}
class LongRunningConversationEvent {
private long timeout;
private String id;
...
}
{code}
Finally we could add two qualifiers for begin() {{@Begun}} and end() {{@Ended}}...
Specify @Destroyed event payload type for a timed-out conversation
------------------------------------------------------------------
Key: CDI-207
URL: https://issues.jboss.org/browse/CDI-207
Project: CDI Specification Issues
Issue Type: Clarification
Components: Contexts
Affects Versions: 1.1.EDR
Reporter: Jozef Hartinger
Assignee: Pete Muir
Fix For: 1.1.PRD
{quote}An event with the ServletRequestEvent as the payload and with qualifier
@Initialized(ConversationContext.class) is fired when the conversation context is
initialized and an event with qualifier @Destroyed(ConversationContext.class) when the
conversation context is destroyed.{quote}
ServletRequestEvent is not available when a conversation is destroyed due to time-out.
--
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