[jboss-jira] [JBoss JIRA] (WFLY-9585) Wildfly 10 ignores jboss-ejb3.xml resource-ref lookup-name

[Shing Lam (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-9585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shing Lam updated WFLY-9585:
----------------------------
    Attachment: jboss-lookup.zip


> Wildfly 10 ignores jboss-ejb3.xml resource-ref lookup-name
> ----------------------------------------------------------
>
>                 Key: WFLY-9585
>                 URL: https://issues.jboss.org/browse/WFLY-9585
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 10.1.0.Final
>         Environment: Wilfly-10.1.0.Final with jdk-1.8.0_31 under Red Hat Enterprise Linux Server release 5.11 (Tikanga)
>            Reporter: Shing Lam
>            Assignee: Tomasz Adamski
>              Labels: Wildfly-10.0.0.Final, datasource, default, jboss-ejb3.xml, lookup-name, resource-ref
>         Attachments: jBossLookup-ear-0.0.1-SNAPSHOT.ear, jBossLookup-ear-0.0.1-SNAPSHOT.ear, jBosslookup.zip, jboss-lookup.zip
>
>
> We have a ear that use a datasource that is injected. The application runs normally in Jboss EAP 6.4, with the correct datasource being used.  But when deployed to Wildfly-10.1.0_Final, instead of the datasource specified in the jboss-ejb3.xml, the default datasource is alway injected.
> We have in the ejb-jar.xml
> {code:xml}
>   <enterprise-beans>
>     <session>
>         <ejb-name>BackgroundRecoverySessionEJB</ejb-name>
>         <resource-ref>
>             <res-ref-name>jdbc/RMDataSource</res-ref-name>
>             <res-type>javax.sql.DataSource</res-type>
>             <res-auth>Container</res-auth>
>         </resource-ref>
>         <persistence-context-ref>
>             <persistence-context-ref-name>persistence/RMEntityManager</persistence-context-ref-name>
>         </persistence-context-ref>
>     </session>
> {code}
> and in jboss-ejb3.xml
> {code:xml}
>   <jboss:enterprise-beans>
>     <jboss:ejb>
>         <ejb-name>BackgroundRecoverySessionEJB</ejb-name>
>         <resource-ref>
>             <res-ref-name>jdbc/RMDataSource</res-ref-name>
>             <res-type>javax.sql.DataSource</res-type>
>             <lookup-name>java:jboss/jdbc/RMDataSource</lookup-name>
>         </resource-ref>
>     </jboss:ejb>
> {code}
> the datasource java:jboss/jdbc/RMDataSource got injected into the EJB under JBoss EAP 6.4.
> But in WildFly 10.1, the default datasource java:jboss/datasources/ExampleDS was injected, causing "org.h2.jdbc.JdbcSQLException: Table "XXX" not found;"
> If we set the default datasource to java:jboss/jdbc/RMDataSource, java:jboss/jdbc/RMDataSource jot injected into the EJB.
> Seems like the jboss-ejb3.xml has no effect on WildFly 10.1, the default datasource is always used.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)