Incorrect Deployment Error
--------------------------
Key: GERONIMO-514
URL: http://nagoya.apache.org/jira/browse/GERONIMO-514
Project: Apache Geronimo
Type: Bug
Components: web, deployment, connector
Reporter: Aaron Mulder
Attempted a web application with a resource reference in web.xml. The Geronimo
deployment plan is:
<web-app
xmlns="http://geronimo.apache.org/xml/ns/web/jetty";
xmlns:naming="http://geronimo.apache.org/xml/ns/naming";
configId="iii"
parentId="org/apache/geronimo/Server">
<context-priority-classloader>true</context-priority-classloader>
<naming:resource-ref>
<naming:ref-name>jdbc/Database</naming:ref-name>
<naming:resource-link>
SystemDatasource
</naming:resource-link>
</naming:resource-ref>
</web-app>
The problem in the above is that whitespace is not stripped on the
resource-link as of this writing. However, the resulting error claims there's
an ejb-link problem, and it really shouldn't since this is a resource ref
problem:
Deployment failed
Server reports: Could not construct connection factory object name query
org.apache.geronimo.common.DeploymentException: Could not construct connection
factory object name query
at
org.apache.geronimo.j2ee.deployment.RefContext.getConnectionFactoryContainerId(RefContext.java:254)
at
org.apache.geronimo.naming.deployment.ENCConfigBuilder.getResourceContainerId(ENCConfigBuilder.java:125)
at
org.apache.geronimo.naming.deployment.ENCConfigBuilder.addResourceRefs(ENCConfigBuilder.java:105)
at
org.apache.geronimo.naming.deployment.ENCConfigBuilder.buildComponentContext(ENCConfigBuilder.java:430)
at
org.apache.geronimo.jetty.deployment.JettyModuleBuilder.buildComponentContext(JettyModuleBuilder.java:393)
...
Caused by: org.apache.geronimo.common.UnknownEJBRefException: Unknown ejb-link:
SystemDatasource
at
org.apache.geronimo.j2ee.deployment.RefContext.getContainerId(RefContext.java:283)
at
org.apache.geronimo.j2ee.deployment.RefContext.getConnectionFactoryContainerId(RefContext.java:248)
... 62 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
