[
https://issues.jboss.org/browse/AS7-2713?page=com.atlassian.jira.plugin.s...
]
Marius Bogoevici reopened AS7-2713:
-----------------------------------
Unfortunately, I can still see the JNDI lookup error with my test project (after a couple
deployments, which makes me believe that the non-deterministic service startup/injection
is still an issue).
Multi-ear war JNDI lookup issues
ServletContextListener.contextInitialized()
----------------------------------------------------------------------------
Key: AS7-2713
URL:
https://issues.jboss.org/browse/AS7-2713
Project: Application Server 7
Issue Type: Bug
Components: Server
Affects Versions: 7.1.0.Alpha1
Reporter: Marius Bogoevici
Assignee: Stuart Douglas
Fix For: 7.1.0.Beta1
The offending application is an EAR with 2 WARs (one uses JSF, one doesn't). It can
be found in
https://gist.github.com/1380689. Each WAR contains a listener which upon start
performs a lookup to java:jboss/datasources/ExampleDS.
Scenario to reproduce: build application, deploy in running instance. Most of the time
the first deployment succeeds. Upon a subsequent deployment, the application fails with a
naming lookup error on the datasource in the JSF jar. The cause is that the
NamespaceContextSelector doesn't have the jboss namespace setup (none of them,
actually).
--
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