[jboss-jira] [JBoss JIRA] Updated: (AS7-1171) relative names that start with "java:XXX", XXX must be: "comp", "module", "app", "global", "jboss"

[Scott Marlow (JIRA)]

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

Scott Marlow updated AS7-1171:
------------------------------

            Summary: relative names that start with "java:XXX", XXX must be: "comp", "module", "app", "global","jboss"  (was: datasource names that start with java:jdbc/ do not work)
        Description: 
Using a datasource name like "java:jdbc/eFpDataSource" in a persistence.xml doesn't seem to work.  We seem to start to deploy the datasource but cannot resolve the service lookup.

Deploying an application that contains a persistence unit reference to the above datasource (see forum post for efp.ear zip), leads to the following server.log output:

07:20:11,374 DEBUG [org.jboss.as.connector.deployer.dsdeployer] (MSC service thread 1-1) Adding datasource: java:/java:jdbc/eFpDataSource

07:20:11,378 TRACE [org.jboss.as.naming.service.BinderService] (MSC service thread 1-2) Bound resource jdbc/eFpDataSource into naming store org.jboss.as.naming.InMemoryNamingStore at 65499154

And the application (includes persistence.xml reference to EfpDataSource) fails to deploy, with the following:
   New missing/unsatisfied dependencies:
      service jboss.naming.context.java.java:jdbc/eFpDataSource (missing)

Instead, we should get a naming ("invalid name") exception when the datasource is added.


  was:
Using a datasource name like "java:jdbc/eFpDataSource" in a persistence.xml doesn't seem to work.  We seem to start to deploy the datasource but cannot resolve the service lookup.

Deploying an application that contains a persistence unit reference to the above datasource (see forum post for efp.ear zip), leads to the following server.log output:

07:20:11,374 DEBUG [org.jboss.as.connector.deployer.dsdeployer] (MSC service thread 1-1) Adding datasource: java:/java:jdbc/eFpDataSource

07:20:11,378 TRACE [org.jboss.as.naming.service.BinderService] (MSC service thread 1-2) Bound resource jdbc/eFpDataSource into naming store org.jboss.as.naming.InMemoryNamingStore at 65499154

   New missing/unsatisfied dependencies:
      service jboss.naming.context.java.java:jdbc/eFpDataSource (missing)


    Forum Reference: http://community.jboss.org/message/612948, http://lists.jboss.org/pipermail/jboss-as7-dev/2011-July/thread.html#2879  (was: http://community.jboss.org/message/612948, http://lists.jboss.org/pipermail/jboss-as7-dev/2011-July/thread.html#2879)


> relative names that start with "java:XXX", XXX must be: "comp", "module", "app", "global","jboss"
> -------------------------------------------------------------------------------------------------
>
>                 Key: AS7-1171
>                 URL: https://issues.jboss.org/browse/AS7-1171
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: JCA
>    Affects Versions: 7.0.0.CR1
>            Reporter: Scott Marlow
>            Assignee: John Bailey
>             Fix For: 7.0.0.Final
>
>
> Using a datasource name like "java:jdbc/eFpDataSource" in a persistence.xml doesn't seem to work.  We seem to start to deploy the datasource but cannot resolve the service lookup.
> Deploying an application that contains a persistence unit reference to the above datasource (see forum post for efp.ear zip), leads to the following server.log output:
> 07:20:11,374 DEBUG [org.jboss.as.connector.deployer.dsdeployer] (MSC service thread 1-1) Adding datasource: java:/java:jdbc/eFpDataSource
> 07:20:11,378 TRACE [org.jboss.as.naming.service.BinderService] (MSC service thread 1-2) Bound resource jdbc/eFpDataSource into naming store org.jboss.as.naming.InMemoryNamingStore at 65499154
> And the application (includes persistence.xml reference to EfpDataSource) fails to deploy, with the following:
>    New missing/unsatisfied dependencies:
>       service jboss.naming.context.java.java:jdbc/eFpDataSource (missing)
> Instead, we should get a naming ("invalid name") exception when the datasource is added.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira