You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by "Doughty, Michael" <Mi...@bmc.com> on 2010/05/01 00:01:24 UTC
Issues running Axis2 in Tomcat in directory with spaces
We're having a bit of an issue here running the Axis2 1.5.1 WAR distribution inside of a directory with spaces in its name. Specifically, our Tomcat is under the following:
D:\Program Files\ProactiveNet\pw\tomcat\webapps
5.1 WAR distribution inside of a directory with spaces in its name. Specifically, our Tomcat is under the following:
When we deploy Axis2 to this, with or without services, we get the following sort of errors:
HTTP Status 500 -
--------------------------------------------------------------------------------
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: Unable to compile class for JSP:
An error occurred at line: 6 in the generated java file
D:\Program Files\ProactiveNet\pw\tomcat\work\Catalina\127.0.0.1\atriumws76\org\apache\jsp\axis2_002dweb\include\httpbase_jsp.java:6: package org.apache.axis2 does not exist
import org.apache.axis2.AxisFault;
^
--------------------------------------------------------------------------------
There are actually a lot more errors than that, so I've attached a copy of the HTML source that is being displayed.
Notice that this issue does not happen if we run in a Tomcat without spaces in the directory path. Also, we took a look at the classpath that Tomcat is forming here and it looks like it is being escaped and formatted improperly:
classpath=/D:/Program%20Files/ProactiveNet/pw/tomcat/webapps/atriumws76/WEB-INF/classes/;/D:/Program%20Files/ProactiveNet/pw/t...
Notice the slash at the beginning of the drive name, and the conversion of spaces to %20.
One of our validation links shows the following JRE version: java.runtime.version=1.6.0_16-b01. I know some issues existed previously with 1.6 JDK, but I thought this revision would have that issue resolved.
Does anyone have an idea what the problem is or how we can fix it?