[jboss-jira] [JBoss JIRA] (WFLY-5213) Injecting external context to Artemis fails

[Jeff Mesnil (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13307664#comment-13307664 ] 

Jeff Mesnil commented on WFLY-5213:
-----------------------------------

I'm not sure this is a correct use case.

If you specify the org.wildfly.extension.messaging-activemq module, the code that injects JMSContext will do a JNDI lookup to locate the TransactionSynchronizationRegistry *in Artemis JNDI*.
As the code is written now, only the JNDI lookup for external resources (Artemis ConnectionFactory) must use external-context.

What's the use case? If you really want to leverage org.wildfly.extension.messaging-activemq module, it is recommended to configure a pooled-connection-factory to connect to a remote Artemis broker as explained in https://docs.jboss.org/author/display/WFLY10/Connect+a+pooled-connection-factory+to+a+Remote+Artemis+Server?_sscc=t


> Injecting external context to Artemis fails
> -------------------------------------------
>
>                 Key: WFLY-5213
>                 URL: https://issues.jboss.org/browse/WFLY-5213
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 10.0.0.Beta2
>            Reporter: Ondřej Kalman
>            Assignee: Jeff Mesnil
>             Fix For: 10.0.0.CR1
>
>
> When external-context is defined in EAP and it's pointing to external Artemis broker, it can't be injected in to MDB via @Resource(lookup = "java:global/externalcontext"). Such injection results in null object.
> Injecting destinations from external context results in javax.ejb.EJBTransactionRolledbackException.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)