[jboss-jira] [JBoss JIRA] (AS7-2597) Cannot use same binding name in resource-ref
[
https://issues.jboss.org/browse/AS7-2597?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-2597:
-----------------------------------
The change here (compared) to previous versions is how we translate the <jndi-name>
or even <mapped-name> and <lookup-name>. Note that in the config:
{code:xml}
<jboss-web>
<resource-ref>
<res-ref-name>eis/JAXR</res-ref-name>
<jndi-name>eis/JAXR</jndi-name>
</resource-ref>
</jboss-web>
{code}
The res-ref-name should translate to java:comp/env/eis/JAXR. Whereas the jndi-name
translates to the global namespace (in previous versions of AS). So it really isn't a
circular binding. I'm not sure how we deal with the jndi-name in latest AS7 upstream.
Do we consider it to be relative to some specific namespace?
Ultimately, for configs like these IMO, we either throw an error since no explicit
namespace is specified for jndi-name or consider it relative to java:jboss/ namespace by
default.
Cannot use same binding name in resource-ref
---------------------------------------------
Key: AS7-2597
URL: https://issues.jboss.org/browse/AS7-2597
Project: Application Server 7
Issue Type: Bug
Components: Naming
Reporter: Thomas Diesler
Assignee: John Bailey
Fix For: 7.1.0.CR1
Using this mapping (as the TCK does)
{code}
<jboss-web>
<resource-ref>
<res-ref-name>eis/JAXR</res-ref-name>
<jndi-name>eis/JAXR</jndi-name>
</resource-ref>
</jboss-web>
{code}
I get
{code}
17:56:29,921 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed
to start service jboss.deployment.unit."jaxr-connection-test.war".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."jaxr-connection-test.war".INSTALL: Failed to process
phase INSTALL of deployment "jaxr-connection-test.war"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
[jboss-as-server-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_29]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_29]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_29]
Caused by: org.jboss.msc.service.CircularDependencyException: Service jboss-as has a
circular dependency
at
org.jboss.msc.service.ServiceContainerImpl.detectCircularity(ServiceContainerImpl.java:617)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
org.jboss.msc.service.ServiceContainerImpl.detectCircularity(ServiceContainerImpl.java:588)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:562)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2211)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2211)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor.addJndiBinding(ModuleJndiBindingProcessor.java:212)
at
org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:103)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
[jboss-as-server-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira