Is this an acceptable geronimo-jetty.xml, are all paths relative to target/repository?
Yes, this should work (assuming you've copied the jars into target/repository) - please can you open a bug in Jira. Workaround info is below
<?xml version="1.0" encoding="UTF-8"?>
<web-app
xmlns="http://geronimo.apache.org/xml/ns/web/jetty";
configId="your/domain/name/j2eetutorialhelloservice"
parentId="org/apache/geronimo/Server">
<context-root>/j2eetutorialhelloservice</context-root>
<context-priority-classloader>false</context-priority-classloader>
<dependency>
<uri>axis/jars/activation.jar</uri>
<uri>axis/jars/commons-logging.jar</uri>
<uri>axis/jars/saaj.jar</uri>
<uri>axis/jars/axis-ant.jar</uri>
<uri>axis/jars/jaxrpc.jar</uri>
<uri>axis/jars/wsdl4j.jar</uri>
<uri>axis/jars/axis.jar</uri>
<uri>axis/jars/log4j-1.2.8.jar</uri>
<uri>axis/jars/xmlsec.jar</uri>
<uri>axis/jars/commons-discovery.jar</uri>
<uri>axis/jars/mail.jar</uri>
</dependency>
</web-app>
When I do this the servlet classes are not found. Are there other ways of configuring Axis and Geronimo.
I'm assuming you mean the axis classes rather than javax.servlet.*
I think this is a problem with the WAR deployer not getting the dependency classpath right. A workaround would be to build a pure GBean configuration (like server-plan.xml) which just contained these dependencies and make your WAR's parent config that rather than the o/a/g/Server one. Something like:
<?xml version="1.0" encoding="UTF-8"?>
<configuration
xmlns="http://geronimo.apache.org/xml/ns/deployment";
configId="your/domain/name/axisHack"
parentId="org/apache/geronimo/Server"
>
<dependency>
<uri>axis/jars/activation.jar</uri>
<uri>axis/jars/commons-logging.jar</uri>
<uri>axis/jars/saaj.jar</uri>
<uri>axis/jars/axis-ant.jar</uri>
<uri>axis/jars/jaxrpc.jar</uri>
<uri>axis/jars/wsdl4j.jar</uri>
<uri>axis/jars/axis.jar</uri>
<uri>axis/jars/log4j-1.2.8.jar</uri>
<uri>axis/jars/xmlsec.jar</uri>
<uri>axis/jars/commons-discovery.jar</uri>
<uri>axis/jars/mail.jar</uri>
</dependency>
</configuration>Alternatively, you can add the dependencies into the Server config and redeploy it (yuck), or just put the jars in your WAR until this is fixed.
-- Jeremy
