3:19 p.m.
Support @EJB injection
-----------------------
Key: ARQ-77
URL: https://jira.jboss.org/jira/browse/ARQ-77
Project: Arquillian
Issue Type: Feature Request
Components: OpenEJB Containers
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
Tests should be able to have class or instance members injected according to @EJB
semantics, avoiding the need for lookup code. The prototype is currently in the OpenEJB
integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible
resolvers (which need an EJB name, module name, app name, and business interface name).
Note that portable JNDI is under java:global, so only accessible to local JVMs.
--
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
3:44 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-77) Support @EJB injection
[
https://jira.jboss.org/jira/browse/ARQ-77?page=com.atlassian.jira.plugin....
]
Aslak Knutsen commented on ARQ-77:
----------------------------------
http://fisheye.jboss.org/changelog/JBossCommon/?cs=4078
Added initial EJB injection support by extending the EJBInjectionEnricher. providing a new
InitialContext and some resolving logic/magic.
OpenEJB does not seem to follow the EJB 3.1 JNDI naming strategy.
Support @EJB injection
-----------------------
Key: ARQ-77
URL: https://jira.jboss.org/jira/browse/ARQ-77
Project: Arquillian
Issue Type: Feature Request
Components: OpenEJB Containers
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
Tests should be able to have class or instance members injected according to @EJB
semantics, avoiding the need for lookup code. The prototype is currently in the OpenEJB
integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible
resolvers (which need an EJB name, module name, app name, and business interface name).
Note that portable JNDI is under java:global, so only accessible to local JVMs.
--
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 a.m.
New subject: [JBoss JIRA] Updated: (ARQ-77) Support @EJB injection
[
https://jira.jboss.org/jira/browse/ARQ-77?page=com.atlassian.jira.plugin....
]
Aslak Knutsen updated ARQ-77:
-----------------------------
Component/s: GlassFish Containers
JBoss Containers
Packaging Enricher SPI
Support @EJB injection
-----------------------
Key: ARQ-77
URL: https://jira.jboss.org/jira/browse/ARQ-77
Project: Arquillian
Issue Type: Feature Request
Components: GlassFish Containers, JBoss Containers, OpenEJB Containers,
Packaging Enricher SPI
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
Tests should be able to have class or instance members injected according to @EJB
semantics, avoiding the need for lookup code. The prototype is currently in the OpenEJB
integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible
resolvers (which need an EJB name, module name, app name, and business interface name).
Note that portable JNDI is under java:global, so only accessible to local JVMs.
--
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:16 p.m.
New subject: [JBoss JIRA] Updated: (ARQ-77) Support @EJB injection
[
https://jira.jboss.org/browse/ARQ-77?page=com.atlassian.jira.plugin.syste...
]
Aslak Knutsen updated ARQ-77:
-----------------------------
Issue Type: Bug (was: Feature Request)
Affects Version/s: 1.0.0.CR1
Priority: Critical (was: Major)
Support @EJB injection
-----------------------
Key: ARQ-77
URL: https://jira.jboss.org/browse/ARQ-77
Project: Arquillian
Issue Type: Bug
Components: GlassFish Containers, JBoss Containers, OpenEJB Containers,
Packaging Enricher SPI
Affects Versions: 1.0.0.Alpha1, 1.0.0.Alpha2
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
Priority: Critical
Fix For: 1.0.0.CR1
Tests should be able to have class or instance members injected according to @EJB
semantics, avoiding the need for lookup code. The prototype is currently in the OpenEJB
integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible
resolvers (which need an EJB name, module name, app name, and business interface name).
Note that portable JNDI is under java:global, so only accessible to local JVMs.
--
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
4:16 p.m.
New subject: [JBoss JIRA] Updated: (ARQ-77) Support @EJB injection
[
https://jira.jboss.org/browse/ARQ-77?page=com.atlassian.jira.plugin.syste...
]
Aslak Knutsen updated ARQ-77:
-----------------------------
Fix Version/s: 1.0.0.CR1
Affects Version/s: 1.0.0.Alpha2
1.0.0.Alpha1
(was: 1.0.0.CR1)
Support @EJB injection
-----------------------
Key: ARQ-77
URL: https://jira.jboss.org/browse/ARQ-77
Project: Arquillian
Issue Type: Bug
Components: GlassFish Containers, JBoss Containers, OpenEJB Containers,
Packaging Enricher SPI
Affects Versions: 1.0.0.Alpha1, 1.0.0.Alpha2
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
Priority: Critical
Fix For: 1.0.0.CR1
Tests should be able to have class or instance members injected according to @EJB
semantics, avoiding the need for lookup code. The prototype is currently in the OpenEJB
integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible
resolvers (which need an EJB name, module name, app name, and business interface name).
Note that portable JNDI is under java:global, so only accessible to local JVMs.
--
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
3:28 p.m.
New subject: [JBoss JIRA] Updated: (ARQ-77) Support @EJB injection with proper semantics
[
https://jira.jboss.org/browse/ARQ-77?page=com.atlassian.jira.plugin.syste...
]
Dan Allen updated ARQ-77:
-------------------------
Summary: Support @EJB injection with proper semantics (was: Support @EJB injection )
Updated title to be more clear this is an improvement request.
Support @EJB injection with proper semantics
--------------------------------------------
Key: ARQ-77
URL: https://jira.jboss.org/browse/ARQ-77
Project: Arquillian
Issue Type: Bug
Components: GlassFish Containers, JBoss Containers, OpenEJB Containers,
Packaging Enricher SPI
Affects Versions: 1.0.0.Alpha1, 1.0.0.Alpha2
Reporter: Andrew Rubinger
Assignee: Andrew Rubinger
Priority: Critical
Fix For: 1.0.0.CR1
Tests should be able to have class or instance members injected according to @EJB
semantics, avoiding the need for lookup code. The prototype is currently in the OpenEJB
integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible
resolvers (which need an EJB name, module name, app name, and business interface name).
Note that portable JNDI is under java:global, so only accessible to local JVMs.
--
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
3:34 p.m.
New subject: [JBoss JIRA] Updated: (ARQ-77) Support @EJB injection with proper semantics
[
https://issues.jboss.org/browse/ARQ-77?page=com.atlassian.jira.plugin.sys...
]
Aslak Knutsen updated ARQ-77:
-----------------------------
Fix Version/s: 1.0.0.Final
(was: 1.0.0.CR1)
Support @EJB injection with proper semantics
--------------------------------------------
Key: ARQ-77
URL: https://issues.jboss.org/browse/ARQ-77
Project: Arquillian
Issue Type: Bug
Components: GlassFish Containers, JBoss Containers, OpenEJB Containers,
Packaging Enricher SPI
Affects Versions: 1.0.0.Alpha1, 1.0.0.Alpha2
Reporter: Andrew Rubinger
Assignee: Andrew Rubinger
Priority: Critical
Fix For: 1.0.0.Final
Tests should be able to have class or instance members injected according to @EJB
semantics, avoiding the need for lookup code. The prototype is currently in the OpenEJB
integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible
resolvers (which need an EJB name, module name, app name, and business interface name).
Note that portable JNDI is under java:global, so only accessible to local JVMs.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:48 a.m.
New subject: [JBoss JIRA] Updated: (ARQ-77) Support @EJB injection with proper semantics
[
https://issues.jboss.org/browse/ARQ-77?page=com.atlassian.jira.plugin.sys...
]
Aslak Knutsen updated ARQ-77:
-----------------------------
Fix Version/s: (was: 1.0.0.Final)
Until there are new API/SPI available in the EE platform, or we are included in the
AppServer core, this is impossible to do.
UnSchedule from fixed version.
Support @EJB injection with proper semantics
--------------------------------------------
Key: ARQ-77
URL: https://issues.jboss.org/browse/ARQ-77
Project: Arquillian
Issue Type: Bug
Components: GlassFish Containers, JBoss Containers, OpenEJB Containers,
Packaging Enricher SPI
Affects Versions: 1.0.0.Alpha1, 1.0.0.Alpha2
Reporter: Andrew Rubinger
Assignee: Andrew Rubinger
Priority: Critical
Tests should be able to have class or instance members injected according to @EJB
semantics, avoiding the need for lookup code. The prototype is currently in the OpenEJB
integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible
resolvers (which need an EJB name, module name, app name, and business interface name).
Note that portable JNDI is under java:global, so only accessible to local JVMs.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:32 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-77) Support @EJB injection with proper semantics
[
https://issues.jboss.org/browse/ARQ-77?page=com.atlassian.jira.plugin.sys...
]
Pedro Kowalski commented on ARQ-77:
-----------------------------------
Any progress about this task?
Recently I had to inject EJB's using it's local business interface which had 2
implementations (none of them was resolved by simply adding "Bean" suffix), so
in order to make it working I had to do some dirty hacks with 'mappedBy'
attribute.
We could add the 'beanName' attribute-awareness to the EJB-enricher (similarly to
the mappedBy), but I don't know if it does make any sense if more heavy refactoring is
supposed to happen?
Support @EJB injection with proper semantics
--------------------------------------------
Key: ARQ-77
URL: https://issues.jboss.org/browse/ARQ-77
Project: Arquillian
Issue Type: Bug
Components: GlassFish Containers, JBoss Containers, OpenEJB Containers,
Packaging Enricher SPI
Affects Versions: 1.0.0.Alpha1, 1.0.0.Alpha2
Reporter: Andrew Rubinger
Assignee: Andrew Rubinger
Priority: Critical
Tests should be able to have class or instance members injected according to @EJB
semantics, avoiding the need for lookup code. The prototype is currently in the OpenEJB
integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible
resolvers (which need an EJB name, module name, app name, and business interface name).
Note that portable JNDI is under java:global, so only accessible to local JVMs.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:58 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (ARQ-77) Support @EJB injection with proper semantics
[
https://issues.jboss.org/browse/ARQ-77?page=com.atlassian.jira.plugin.sys...
]
Aslak Knutsen edited comment on ARQ-77 at 9/5/11 11:57 AM:
-----------------------------------------------------------
There is currently nothing we can do with the EJB enrichment without getting hooks into
all EJB Containers(not going to happen over night).
Something like:
@EJB(beanName="MyTestBean")
private TestBean bean;
Could attempt to lookup:
java:/module/beanName!TestBean
java:/module/beanName
?
was (Author: aslak):
There is currently nothing we can do with the EJB enrichment without getting EJB hooks
into all EJB Containers(not going to happen over night).
Something like:
@EJB(beanName="MyTestBean")
private TestBean bean;
Could attempt to lookup:
java:/module/beanName!TestBean
java:/module/beanName
?
Support @EJB injection with proper semantics
--------------------------------------------
Key: ARQ-77
URL: https://issues.jboss.org/browse/ARQ-77
Project: Arquillian
Issue Type: Bug
Components: GlassFish Containers, JBoss Containers, OpenEJB Containers,
Packaging Enricher SPI
Affects Versions: 1.0.0.Alpha1, 1.0.0.Alpha2
Reporter: Andrew Rubinger
Assignee: Andrew Rubinger
Priority: Critical
Tests should be able to have class or instance members injected according to @EJB
semantics, avoiding the need for lookup code. The prototype is currently in the OpenEJB
integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible
resolvers (which need an EJB name, module name, app name, and business interface name).
Note that portable JNDI is under java:global, so only accessible to local JVMs.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:58 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (ARQ-77) Support @EJB injection with proper semantics
[
https://issues.jboss.org/browse/ARQ-77?page=com.atlassian.jira.plugin.sys...
]
Aslak Knutsen edited comment on ARQ-77 at 9/5/11 11:58 AM:
-----------------------------------------------------------
There is currently nothing we can do with the EJB enrichment without getting hooks into
all EJB Containers(not going to happen over night).
Something like:
@EJB(beanName="MyTestBean")
private TestBean bean;
Could attempt to lookup:
java:/module/MyTestBean!TestBean
java:/module/MyTestBean
?
was (Author: aslak):
There is currently nothing we can do with the EJB enrichment without getting hooks
into all EJB Containers(not going to happen over night).
Something like:
@EJB(beanName="MyTestBean")
private TestBean bean;
Could attempt to lookup:
java:/module/beanName!TestBean
java:/module/beanName
?
Support @EJB injection with proper semantics
--------------------------------------------
Key: ARQ-77
URL: https://issues.jboss.org/browse/ARQ-77
Project: Arquillian
Issue Type: Bug
Components: GlassFish Containers, JBoss Containers, OpenEJB Containers,
Packaging Enricher SPI
Affects Versions: 1.0.0.Alpha1, 1.0.0.Alpha2
Reporter: Andrew Rubinger
Assignee: Andrew Rubinger
Priority: Critical
Tests should be able to have class or instance members injected according to @EJB
semantics, avoiding the need for lookup code. The prototype is currently in the OpenEJB
integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible
resolvers (which need an EJB name, module name, app name, and business interface name).
Note that portable JNDI is under java:global, so only accessible to local JVMs.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:58 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-77) Support @EJB injection with proper semantics
[
https://issues.jboss.org/browse/ARQ-77?page=com.atlassian.jira.plugin.sys...
]
Aslak Knutsen commented on ARQ-77:
----------------------------------
There is currently nothing we can do with the EJB enrichment without getting EJB hooks
into all EJB Containers(not going to happen over night).
Something like:
@EJB(beanName="MyTestBean")
private TestBean bean;
Could attempt to lookup:
java:/module/beanName!TestBean
java:/module/beanName
?
Support @EJB injection with proper semantics
--------------------------------------------
Key: ARQ-77
URL: https://issues.jboss.org/browse/ARQ-77
Project: Arquillian
Issue Type: Bug
Components: GlassFish Containers, JBoss Containers, OpenEJB Containers,
Packaging Enricher SPI
Affects Versions: 1.0.0.Alpha1, 1.0.0.Alpha2
Reporter: Andrew Rubinger
Assignee: Andrew Rubinger
Priority: Critical
Tests should be able to have class or instance members injected according to @EJB
semantics, avoiding the need for lookup code. The prototype is currently in the OpenEJB
integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible
resolvers (which need an EJB name, module name, app name, and business interface name).
Note that portable JNDI is under java:global, so only accessible to local JVMs.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:35 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-77) Support @EJB injection with proper semantics
[
https://issues.jboss.org/browse/ARQ-77?page=com.atlassian.jira.plugin.sys...
]
Pedro Kowalski commented on ARQ-77:
-----------------------------------
Yeah, that's exactly what I was thinking of - to support at least some of the portable
JNDI, so:
java:module/<bean-name>[!<fully-qualified-interface-name>]
Support @EJB injection with proper semantics
--------------------------------------------
Key: ARQ-77
URL: https://issues.jboss.org/browse/ARQ-77
Project: Arquillian
Issue Type: Bug
Components: GlassFish Containers, JBoss Containers, OpenEJB Containers,
Packaging Enricher SPI
Affects Versions: 1.0.0.Alpha1, 1.0.0.Alpha2
Reporter: Andrew Rubinger
Assignee: Andrew Rubinger
Priority: Critical
Tests should be able to have class or instance members injected according to @EJB
semantics, avoiding the need for lookup code. The prototype is currently in the OpenEJB
integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible
resolvers (which need an EJB name, module name, app name, and business interface name).
Note that portable JNDI is under java:global, so only accessible to local JVMs.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:41 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (ARQ-77) Support @EJB injection with proper semantics
[
https://issues.jboss.org/browse/ARQ-77?page=com.atlassian.jira.plugin.sys...
]
Pedro Kowalski edited comment on ARQ-77 at 9/6/11 5:40 AM:
-----------------------------------------------------------
Yeah, that's exactly what I was thinking of - to support at least some of the portable
JNDI, so:
java:module/<bean-name>[!<fully-qualified-interface-name>]
EDIT: Oh, and I guess that if one specifies both - mappedName and beanName it should throw
an exception, as I don't see real use of specifying both values at the same time,
right?
was (Author: PedroKowalski):
Yeah, that's exactly what I was thinking of - to support at least some of the
portable JNDI, so:
java:module/<bean-name>[!<fully-qualified-interface-name>]
Support @EJB injection with proper semantics
--------------------------------------------
Key: ARQ-77
URL: https://issues.jboss.org/browse/ARQ-77
Project: Arquillian
Issue Type: Bug
Components: GlassFish Containers, JBoss Containers, OpenEJB Containers,
Packaging Enricher SPI
Affects Versions: 1.0.0.Alpha1, 1.0.0.Alpha2
Reporter: Andrew Rubinger
Assignee: Andrew Rubinger
Priority: Critical
Tests should be able to have class or instance members injected according to @EJB
semantics, avoiding the need for lookup code. The prototype is currently in the OpenEJB
integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible
resolvers (which need an EJB name, module name, app name, and business interface name).
Note that portable JNDI is under java:global, so only accessible to local JVMs.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:05 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-77) Support @EJB injection with proper semantics
[
https://issues.jboss.org/browse/ARQ-77?page=com.atlassian.jira.plugin.sys...
]
Aslak Knutsen commented on ARQ-77:
----------------------------------
yea, agree
Support @EJB injection with proper semantics
--------------------------------------------
Key: ARQ-77
URL: https://issues.jboss.org/browse/ARQ-77
Project: Arquillian
Issue Type: Bug
Components: GlassFish Containers, JBoss Containers, OpenEJB Containers,
Packaging Enricher SPI
Affects Versions: 1.0.0.Alpha1, 1.0.0.Alpha2
Reporter: Andrew Rubinger
Assignee: Andrew Rubinger
Priority: Critical
Tests should be able to have class or instance members injected according to @EJB
semantics, avoiding the need for lookup code. The prototype is currently in the OpenEJB
integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible
resolvers (which need an EJB name, module name, app name, and business interface name).
Note that portable JNDI is under java:global, so only accessible to local JVMs.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:46 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-77) Support @EJB injection with proper semantics
[
https://issues.jboss.org/browse/ARQ-77?page=com.atlassian.jira.plugin.sys...
]
Pedro Kowalski commented on ARQ-77:
-----------------------------------
Pull request sent (https://github.com/arquillian/arquillian-core/pull/22)
Support @EJB injection with proper semantics
--------------------------------------------
Key: ARQ-77
URL: https://issues.jboss.org/browse/ARQ-77
Project: Arquillian
Issue Type: Bug
Components: GlassFish Containers, JBoss Containers, OpenEJB Containers,
Packaging Enricher SPI
Affects Versions: 1.0.0.Alpha1, 1.0.0.Alpha2
Reporter: Andrew Rubinger
Assignee: Andrew Rubinger
Priority: Critical
Tests should be able to have class or instance members injected according to @EJB
semantics, avoiding the need for lookup code. The prototype is currently in the OpenEJB
integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible
resolvers (which need an EJB name, module name, app name, and business interface name).
Note that portable JNDI is under java:global, so only accessible to local JVMs.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:36 a.m.
New subject: [JBoss JIRA] (ARQ-77) Support @EJB injection with proper semantics
[
https://issues.jboss.org/browse/ARQ-77?page=com.atlassian.jira.plugin.sys...
]
Arnold Johansson commented on ARQ-77:
-------------------------------------
So the pull-request has been pushed upstream by Aslak about a year ago. Great! -But
when/where is the solution out? I for one think this is one of the more vital cases that
neddes to be sorted and released as lots of organizations really want to use the otherwise
excellent Arquillian but just can't due to this (@Inject just isn't an option).
Support @EJB injection with proper semantics
--------------------------------------------
Key: ARQ-77
URL: https://issues.jboss.org/browse/ARQ-77
Project: Arquillian
Issue Type: Bug
Components: GlassFish Containers, JBoss AS Containers, OpenEJB Containers,
Packaging Enricher SPI
Affects Versions: 1.0.0.Alpha1, 1.0.0.Alpha2
Reporter: Andrew Rubinger
Assignee: Andrew Rubinger
Priority: Critical
Tests should be able to have class or instance members injected according to @EJB
semantics, avoiding the need for lookup code. The prototype is currently in the OpenEJB
integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible
resolvers (which need an EJB name, module name, app name, and business interface name).
Note that portable JNDI is under java:global, so only accessible to local JVMs.
--
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
4189
days inactive
5197
days old
arquillian-issues@lists.jboss.org
16 comments
5 participants
participants (5)
-
Andrew Lee Rubinger (JIRA) -
Arnold Johansson (JIRA)
-
Aslak Knutsen (JIRA)
-
Dan Allen (JIRA)
-
Pedro Kowalski (JIRA)