[
https://jira.jboss.org/jira/browse/WELD-271?page=com.atlassian.jira.plugi...
]
Nicklas Karlsson commented on WELD-271:
---------------------------------------
It's natural to inject a ConversationManager into the conversation implementation and
use that for the following:
* Checking if the conversation context is active (WELD-348)
* Getting a ID for Conversation.begin()
* Checking for duplicate ID in Conversation.begin()
Methods for these should be added to the API and used in the conversation implementation
Rework conversation management code so that it has a well demarcated
api
------------------------------------------------------------------------
Key: WELD-271
URL:
https://jira.jboss.org/jira/browse/WELD-271
Project: Weld
Issue Type: Feature Request
Components: Conversations
Reporter: Pete Muir
Assignee: Nicklas Karlsson
Fix For: 1.1.0.BETA1
Currently conversation control is not well demarcated, and requires calls to a variety of
classes. All of this should be encapsulated in ConversationManager
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira