tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Romain Manni-Bucau (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (TOMEE-1485) JMS 2.0 Provide JMSContext beans
Date Mon, 05 Jan 2015 07:20:35 GMT

     [ https://issues.apache.org/jira/browse/TOMEE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Romain Manni-Bucau resolved TOMEE-1485.
---------------------------------------
    Resolution: Invalid

@John: this section is 100% about CDI. Right it is about "container" but it is ActiveMQ responsability.
There is no reason to bind it to OpenEJB - opposed to JTA which was trivial cause we reused
existing transaction policy of OpenEJB. If AMQ doesnt provide it when we'll integrate we'll
do. However all which is not CDI related and linked to the scanning (@JMS*Definition) is bound
to OpenEJB in AnnotationDeployer.

Note: closing as "Invalid" since I'm not sure which resolution is actually right

> 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)

Mime
View raw message