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

[Ondřej Kalman (JIRA)]

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

Ondřej Kalman edited comment on WFLY-5213 at 10/18/16 8:34 AM:
---------------------------------------------------------------

I checked your client and its fine, on MDB site you have to use @ResourceAdapter(value="remote-artemis")just above "public class MessageConsiumer implements MessageListener ". I think you can safely remove "connectionFactoryLookup"

If you want to use remote broker in all MDBs by default, change "resource-adapter-name" attribute in EJB3 subsystem in your standalone-full.xml


was (Author: okalman):
I checked your client and its fine, on MDB site you have to use @ResourceAdapter(value="remote-artemis")just above "public class MessageConsiumer implements MessageListener ". I think you can safely remove "connectionFactoryLookup"

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