5:51 a.m.
Cody Lerum created CDI-215:
------------------------------
Summary: 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
Reporter: Cody Lerum
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
8:43 p.m.
[
https://issues.jboss.org/browse/CDI-215?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-215:
--------------------------
Component/s: Java EE integration
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
8:43 p.m.
[
https://issues.jboss.org/browse/CDI-215?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-215:
--------------------------
Fix Version/s: 1.1 (Proposed)
Component/s: Contexts
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
3:15 a.m.
[
https://issues.jboss.org/browse/CDI-215?page=com.atlassian.jira.plugin.sy...
]
hantsy bai commented on CDI-215:
--------------------------------
The conversation concept is tided with JSF in CDI 1.0 ...I also encountered problems when
I used @Asynchronous method. I have complained this in the Seam3 forum before.
The scene was the following in my project.
1. user did some operations in the jsf page.
2. the backbean(annotated with @Stateful @Model) processed the request and called a
@Asynchronous method from @Stateless bean to send email to user.
What I expected was the UI will response quickly, but it was blocked by the sending
email.
I am not sure here is the right place to discuss this problem.
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
12:20 p.m.
[
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
1:06 p.m.
[
https://issues.jboss.org/browse/CDI-215?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-215:
-------------------------------
Another way to address this is to allow a scope to propose a "backup" if there
are no active contexts for the scope, in this case @RequestScoped. IOW graceful
degradation.
JMS 2 needs something similar, where they use TX scope if available, otherwise request
scope.
(Not saying I like this approach, but just putting it out there ;-)
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
10:28 p.m.
[
https://issues.jboss.org/browse/CDI-215?page=com.atlassian.jira.plugin.sy...
]
Pete Muir reassigned CDI-215:
-----------------------------
Assignee: Joe Bergmark
Joe, do you want to take this one as it's very closely related to the other issues you
took a look at.
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
Assignee: Joe Bergmark
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
2:15 p.m.
[
https://issues.jboss.org/browse/CDI-215?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-215:
--------------------------
Fix Version/s: 1.1.PRD
(was: 1.1 (Proposed))
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
Assignee: Joe Bergmark
Fix For: 1.1.PRD
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
5:30 p.m.
[
https://issues.jboss.org/browse/CDI-215?page=com.atlassian.jira.plugin.sy...
]
Guido Bonazza commented on CDI-215:
-----------------------------------
This is important to allow for a broader component reuse: it's quite common, I think,
that a component that should be shared in a conversation would make perfect sense without
one (I won't mention the EntityManager anymore of course ;-) but you got the idea).
Probably, if such a temporary conversation is created, Conversation#begin() and
Conversation#end() should fire an exception.
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
Assignee: Joe Bergmark
Fix For: 1.1.PRD
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
4:50 p.m.
[
https://issues.jboss.org/browse/CDI-215?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-215:
--------------------------
Fix Version/s: 1.1.PFD
(was: 1.1.PRD)
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
Assignee: Joe Bergmark
Fix For: 1.1.PFD
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
For more information on JIRA, see: http://www.atlassian.com/software/jira
4197
days inactive
4456
days old
9 comments
5 participants
participants (5)
-
Cody Lerum (JIRA) -
Guido Bonazza (JIRA)
-
hantsy bai (JIRA)
-
Mark Struberg (JIRA)
-
Pete Muir (JIRA)