Jason,
I've been trying to run web tests to get Jetty up and running properly - this is a
strange one....
Try this in testsuite.....
sh ./build.sh -Dtest=web clean test - don't worry about it failing....
[jules@zeuglodon testsuite]$ ls -l `find . -name soap*.jar`
-rw-rw-r-- 1 jules jules 220746 Sep 6 01:33
./output/resources/web/WEB-INF/lib/soap-2_2.jar
-rw-rw-r-- 1 jules jules 220750 Jun 27 11:09
./src/resources/web/WEB-INF/lib/soap-2_2.jar
[jules@zeuglodon testsuite]$
[jules@zeuglodon testsuite]$ jar tvf ./output/resources/web/WEB-INF/lib/soap-2_2.jar
0 Tue Jun 26 13:44:22 BST 2001 META-INF/
java.util.zip.ZipException: invalid entry CRC (expected 0xc7322017 but got
0xde9b8379)
at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:365)
at java.util.zip.ZipInputStream.read(ZipInputStream.java:144)
at java.util.zip.ZipInputStream.closeEntry(ZipInputStream.java:93)
at sun.tools.jar.Main.list(Main.java:744)
at sun.tools.jar.Main.run(Main.java:193)
at sun.tools.jar.Main.main(Main.java:904)
[jules@zeuglodon testsuite]$
Perhaps I'm losing my mind..... but this looks like an ant bug....
Unsurprisingly, when someone calls the MessageRouterServlet Jetty complains ....
javax.servlet.UnavailableException: java.lang.ClassNotFoundException:
org.apache.soap.server.http.MessageRouterServlet
at com.mortbay.Jetty.Servlet.ServletHolder.initializeClass(ServletHolder.java:263)
at com.mortbay.Jetty.Servlet.ServletHandler.start(ServletHandler.java:200)
at com.mortbay.HTTP.HandlerContext.start(HandlerContext.java:1081)
at
com.mortbay.Jetty.Servlet.WebApplicationContext.start(WebApplicationContext.java:354)
at org.jboss.jetty.Jetty.deploy(Jetty.java:196)
at org.jboss.jetty.JettyService.performDeploy(JettyService.java:258)
at org.jboss.web.AbstractWebContainer.deploy(AbstractWebContainer.java:185)
at java.lang.reflect.Method.invoke(Native Method)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at org.jboss.deployment.J2eeDeployer.startModules(J2eeDeployer.java:501)
at org.jboss.deployment.J2eeDeployer.startApplication(J2eeDeployer.java:464)
at org.jboss.deployment.J2eeDeployer.deploy(J2eeDeployer.java:208)
at java.lang.reflect.Method.invoke(Native Method)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at org.jboss.jmx.server.JMXAdaptorImpl.invoke(JMXAdaptorImpl.java:69)
at java.lang.reflect.Method.invoke(Native Method)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:241)
at sun.rmi.transport.Transport$1.run(Transport.java:152)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:148)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:465)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:706)
at java.lang.Thread.run(Thread.java:484)
getRootCause():
If you get past this problem, I have checked back in a couple of changes which
should fix some stuff.
You might want to remove all excess stuff from your jett.xml in conf/Default to get
Jetty to work cleanly - I simply set JettyHome in jboss-service.xml to point at a
valid Jetty-3.1.RC8 tree - no problemo.
Jules
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
