[
https://issues.apache.org/jira/browse/TOMEE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14264530#comment-14264530
]
John D. Ament commented on TOMEE-1485:
--------------------------------------
When we discussed as a part of the JMS expert group, it was decided that CDI
related integrations would be listed within the specs that wanted the
integration. Whether they felt their implementations could do it or if it were
a part of the integration layer required to be on the app server level. This
is opposite to what EJB did (MDBs), where you saw a spec specify what another
spec should do.
In this specific case, unanimously it is done in the integration layer and not
the JMS provider (which is not a container).
I created this as an indicator that the work needs to be in TomEE.
> JMS 2.0 Provide JMSContext beans
> --------------------------------
>
> Key: TOMEE-1485
> URL: https://issues.apache.org/jira/browse/TOMEE-1485
> Project: TomEE
> Issue Type: New Feature
> Reporter: John D. Ament
>
> JMS 2.0 spec requires two beans to be defined - a TransactionScoped instance
> and a RequestScoped instance. The RequestScoped one acts more like a
> dependent bean since its not shared across injection points.
> This is a container level responsibility not the JMS provider. Please see
> Section 12.4 of the JMS Spec for implementation details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
