geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Updated: (GERONIMO-589) Standalone war does not have a default context
Date Sat, 20 Aug 2005 22:45:20 GMT
     [ ]

David Jencks updated GERONIMO-589:

    Assign To: Jeff Genender  (was: David Jencks)

Patch applied with modifications, and defaultContextPriorityClassloader added to tomcat builder
as well.  I'm not sure if the tomcat builder produces a context root for a standalone web-app
with a plan without a context root element.  Jeff, can you look into this and fix it if you
think it's appropriate?

Sending        trunk/modules/assembly/src/plan/jetty-deployer-config.xml
Sending        trunk/modules/assembly/src/plan/jetty-runtime-deployer-config.xml
Sending        trunk/modules/assembly/src/plan/tomcat-deployer-config.xml
Sending        trunk/modules/assembly/src/plan/tomcat-runtime-deployer-config.xml
Sending        trunk/modules/jetty-builder/src/java/org/apache/geronimo/jetty/deployment/
Sending        trunk/modules/jetty-builder/src/test/org/apache/geronimo/jetty/deployment/
Sending        trunk/modules/jetty-builder/src/test/org/apache/geronimo/jetty/deployment/
Sending        trunk/modules/tomcat-builder/src/java/org/apache/geronimo/tomcat/deployment/
Sending        trunk/modules/tomcat-builder/src/test/org/apache/geronimo/tomcat/deployment/
Sending        trunk/modules/tomcat-builder/src/test/org/apache/geronimo/tomcat/deployment/
Sending        trunk/modules/web-builder/src/schema/geronimo-web.xsd
Transmitting file data ...........
Committed revision 234133.

> Standalone war does not have a default context
> ----------------------------------------------
>          Key: GERONIMO-589
>          URL:
>      Project: Geronimo
>         Type: Bug
>   Components: web
>     Versions: 1.0-M3
>     Reporter: Dain Sundstrom
>     Assignee: Jeff Genender
>      Fix For: 1.0-M5
>  Attachments: patch.tar.gz
> If I have a standalone war with the following deployment plan:
> <?xml version="1.0" encoding="UTF-8"?>
> <web-app xmlns=""
>     configId="foo"
>     parentId="org/apache/geronimo/Server">
>     <context-priority-classloader>false</context-priority-classloader>
> </web-app>
> The module will deploy, but the following exception is thrown on startup:
> java.lang.IllegalArgumentException: Illegal context spec:null
>         at org.mortbay.http.HttpContext.canonicalContextPathSpec(
>         at org.mortbay.http.HttpContext.setContextPath(
>         at org.mortbay.http.HttpContext$$FastClassByCGLIB$$c359e803.invoke(<generated>)
>         at net.sf.cglib.reflect.FastMethod.invoke(
>         at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(
>         at org.apache.geronimo.gbean.runtime.GBeanAttribute.setValue(
>         at org.apache.geronimo.gbean.runtime.GBeanAttribute.inject(
>         at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(
>         at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(
>         at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(
>         at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(
>         at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(
>         at org.apache.geronimo.kernel.Kernel.startRecursiveGBean(
> This can be fixed by adding a context-root element to the deployment plan.  Either the
context-root element should be required, or preferably set the default context to the configuration
id which is the default in the case where you have no deployment plan.  Also the context-priority-classloader
element should be optional.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message