[
https://issues.jboss.org/browse/CDI-215?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-215:
-----------------------------------
@Asynchronous and @ConversationScoped is not a good team anyway.
a.) @Asynchronous is fire and forget. There is no reliance guarantee nor TX, etc.
Currently there is also no CDI Context propagation defined in the EJB spec.
b.) @ConversationScoped beans are 'bound' to by a single thread. They must not get
accessed from multiple threads. The intention was to keep them EntityManager safe it
seems. But that is not a good fit for starting async handling at all.
Create temporary Conversation when method invoked from non-servlet
request
--------------------------------------------------------------------------
Key: CDI-215
URL:
https://issues.jboss.org/browse/CDI-215
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts, Java EE integration
Reporter: Cody Lerum
Fix For: 1.1 (Proposed)
Use case would be from an EJB 3.1 Timer
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira