[JBoss JIRA] Created: (EJBTHREE-2020) Refactor EJBContext implementation to allow a global association instead of per EJB
4:28 a.m.
Refactor EJBContext implementation to allow a global association instead of per EJB
-----------------------------------------------------------------------------------
Key: EJBTHREE-2020
URL: https://jira.jboss.org/jira/browse/EJBTHREE-2020
Project: EJB 3.0
Issue Type: Task
Reporter: Carlo de Wolf
Fix For: EJB 3.1
In a web deployment java:comp/EJBContext is shared between multiple EJB containers.
Refactor EJBContext to have an implementation that can be bound globally (for example:
java:internal/global/EJBContext), then LinkRef to that for each java:comp/EJBContext.
--
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
7:05 a.m.
New subject: [JBoss JIRA] Assigned: (EJBTHREE-2020) Refactor EJBContext implementation to allow a global association instead of per EJB
[
https://jira.jboss.org/jira/browse/EJBTHREE-2020?page=com.atlassian.jira....
]
Carlo de Wolf reassigned EJBTHREE-2020:
---------------------------------------
Assignee: Carlo de Wolf
Refactor EJBContext implementation to allow a global association
instead of per EJB
-----------------------------------------------------------------------------------
Key: EJBTHREE-2020
URL: https://jira.jboss.org/jira/browse/EJBTHREE-2020
Project: EJB 3.0
Issue Type: Task
Reporter: Carlo de Wolf
Assignee: Carlo de Wolf
Fix For: EJB 3.1
In a web deployment java:comp/EJBContext is shared between multiple EJB containers.
Refactor EJBContext to have an implementation that can be bound globally (for example:
java:internal/global/EJBContext), then LinkRef to that for each java:comp/EJBContext.
--
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
8:15 a.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-2020) Refactor EJBContext implementation to allow a global association instead of per EJB
[
https://jira.jboss.org/jira/browse/EJBTHREE-2020?page=com.atlassian.jira....
]
Carlo de Wolf updated EJBTHREE-2020:
------------------------------------
Fix Version/s: EJB3_1 1.0.8
EJB3_1 1.0.7
EJB3_1 1.0.6
(was: EJB 3.1)
Refactor EJBContext implementation to allow a global association
instead of per EJB
-----------------------------------------------------------------------------------
Key: EJBTHREE-2020
URL: https://jira.jboss.org/jira/browse/EJBTHREE-2020
Project: EJB 3.0
Issue Type: Task
Reporter: Carlo de Wolf
Assignee: Carlo de Wolf
Fix For: EJB3_1 1.0.6, EJB3_1 1.0.7, EJB3_1 1.0.8
In a web deployment java:comp/EJBContext is shared between multiple EJB containers.
Refactor EJBContext to have an implementation that can be bound globally (for example:
java:internal/global/EJBContext), then LinkRef to that for each java:comp/EJBContext.
--
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
12:43 p.m.
New subject: [JBoss JIRA] Resolved: (EJBTHREE-2020) Refactor EJBContext implementation to allow a global association instead of per EJB
[
https://jira.jboss.org/jira/browse/EJBTHREE-2020?page=com.atlassian.jira....
]
Carlo de Wolf resolved EJBTHREE-2020.
-------------------------------------
Resolution: Done
Refactor EJBContext implementation to allow a global association
instead of per EJB
-----------------------------------------------------------------------------------
Key: EJBTHREE-2020
URL: https://jira.jboss.org/jira/browse/EJBTHREE-2020
Project: EJB 3.0
Issue Type: Task
Reporter: Carlo de Wolf
Assignee: Carlo de Wolf
Fix For: EJB3_1 1.0.8, EJB3_1 1.0.7, EJB3_1 1.0.6
In a web deployment java:comp/EJBContext is shared between multiple EJB containers.
Refactor EJBContext to have an implementation that can be bound globally (for example:
java:internal/global/EJBContext), then LinkRef to that for each java:comp/EJBContext.
--
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
12:43 p.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-2020) Refactor EJBContext implementation to allow a global association instead of per EJB
[
https://jira.jboss.org/jira/browse/EJBTHREE-2020?page=com.atlassian.jira....
]
Carlo de Wolf updated EJBTHREE-2020:
------------------------------------
Component Fix Version(s): 0.1.1
Refactor EJBContext implementation to allow a global association
instead of per EJB
-----------------------------------------------------------------------------------
Key: EJBTHREE-2020
URL: https://jira.jboss.org/jira/browse/EJBTHREE-2020
Project: EJB 3.0
Issue Type: Task
Reporter: Carlo de Wolf
Assignee: Carlo de Wolf
Fix For: EJB3_1 1.0.6, EJB3_1 1.0.7, EJB3_1 1.0.8
In a web deployment java:comp/EJBContext is shared between multiple EJB containers.
Refactor EJBContext to have an implementation that can be bound globally (for example:
java:internal/global/EJBContext), then LinkRef to that for each java:comp/EJBContext.
--
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
6:26 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-2020) Refactor EJBContext implementation to allow a global association instead of per EJB
[
https://jira.jboss.org/jira/browse/EJBTHREE-2020?page=com.atlassian.jira....
]
Carlo de Wolf commented on EJBTHREE-2020:
-----------------------------------------
Q: I'm getting 'EJBTHREE-2020: No InjectionCallbackStack defined for domain ... of
...'
A: Previously during injection no context was available. The check whether an EJBContext
method was allowed or not would go to the current invocation. After this change there must
always be an InvocationContext available which also services the EJBContext methods. To
make this happen the InjectionCallbackStack is inserted in an injection invocation.
Normally that stack would look like:
<stack name="InjectionCallbackStack">
<interceptor-ref
name="org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor"/>
<interceptor-ref name="CurrentInvocationContextInterceptor"/>
</stack>
The full modifications that are to be made to ejb3-interceptors-aop.xml are here:
http://fisheye.jboss.org/browse/JBossAS/projects/ejb3/trunk/core/src/main...
For reference, the current invocation context is stored here:
http://github.com/wolfc/jboss-ejb3-context/blob/jboss-ejb3-context-0.1.1/...
Refactor EJBContext implementation to allow a global association
instead of per EJB
-----------------------------------------------------------------------------------
Key: EJBTHREE-2020
URL: https://jira.jboss.org/jira/browse/EJBTHREE-2020
Project: EJB 3.0
Issue Type: Task
Reporter: Carlo de Wolf
Assignee: Carlo de Wolf
Fix For: EJB3_1 1.0.6, EJB3_1 1.0.7, EJB3_1 1.0.8
In a web deployment java:comp/EJBContext is shared between multiple EJB containers.
Refactor EJBContext to have an implementation that can be bound globally (for example:
java:internal/global/EJBContext), then LinkRef to that for each java:comp/EJBContext.
--
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
4:22 a.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-2020) Refactor EJBContext implementation to allow a global association instead of per EJB
[
https://jira.jboss.org/browse/EJBTHREE-2020?page=com.atlassian.jira.plugi...
]
Carlo de Wolf updated EJBTHREE-2020:
------------------------------------
Fix Version/s: bom-eap5-0.1.2
Component/s: context
Refactor EJBContext implementation to allow a global association
instead of per EJB
-----------------------------------------------------------------------------------
Key: EJBTHREE-2020
URL: https://jira.jboss.org/browse/EJBTHREE-2020
Project: EJB 3.0
Issue Type: Task
Components: context
Reporter: Carlo de Wolf
Assignee: Carlo de Wolf
Fix For: EJB3_1 1.0.6, EJB3_1 1.0.7, bom-eap5-0.1.2, EJB3_1 1.0.8
In a web deployment java:comp/EJBContext is shared between multiple EJB containers.
Refactor EJBContext to have an implementation that can be bound globally (for example:
java:internal/global/EJBContext), then LinkRef to that for each java:comp/EJBContext.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5873
days inactive
6000
days old
6 comments
1 participants
participants (1)
-
Carlo de Wolf (JIRA)