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] [Commented] (TOMEE-1485) JMS 2.0 Provide JMSContext beans
Date Mon, 05 Jan 2015 13:10:35 GMT

    [ https://issues.apache.org/jira/browse/TOMEE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14264570#comment-14264570
] 

Romain Manni-Bucau commented on TOMEE-1485:
-------------------------------------------

This is exactly what I said you: there is no reason at all to do anything in TomEE excepted
handling XDefinition annotations. All other stuff will be done on activemq side then imported
in TomEE.

There is no link with the "place in the spec". This is what is done for all projects and I
think it is better than writing all the glue in TomEE and preventing other users to use this
part which doesnt need any tomee specific integration, no? What do I miss?

> 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