I have been doing a bit further investigation and edited the source of JWSHandler. Just before the setting of the classpath, I added a debug:
log.debug(getDefaultClasspath(msgContext));
compiler.setClasspath(getDefaultClasspath(msgContext));
This is the classpath that the compiler will use to get the jws file compiled.
Now, running it with debug on gives me the following classpath:
/usr/local/jboss-3.2.2/bin/run.jar:/usr/local/jboss-3.2.2/bin/../client/getopt.jar:/usr/local/j2sdk1.4.1_01/lib/tools.jar:/usr/local/j2sdk1.4.1_01/jre/lib/ext/sunjce_provider.jar:/usr/local/j2sdk1.4.1_01/jre/lib/ext/dnsns.jar:/usr/local/j2sdk1.4.1_01/jre/lib/ext/localedata.jar:/usr/local/j2sdk1.4.1_01/jre/lib/ext/ldapsec.jar:/usr/local/jboss-3.2.2/server/default/deploy/webapps/axis.war/WEB-INF/classes:/usr/local/jboss-3.2.2/server/default/deploy/webapps/axis.war/WEB-INF/lib/axis-ant.jar:/usr/local/jboss-3.2.2/server/default/deploy/webapps/axis.war/WEB-INF/lib/axis.jar:/usr/local/jboss-3.2.2/server/default/deploy/webapps/axis.war/WEB-INF/lib/commons-discovery.jar:/usr/local/jboss-3.2.2/server/default/deploy/webapps/axis.war/WEB-INF/lib/commons-logging.jar:/usr/local/jboss-3.2.2/server/default/deploy/webapps/axis.war/WEB-INF/lib/jaxrpc.jar:/usr/local/jboss-3.2.2/server/default/deploy/webapps/axis.war/WEB-INF/lib/log4j-1.2.8.jar:/usr/local/jboss-3.2.2/server/default/deploy/webapps/axis.war/WEB-INF/lib/saaj.jar:/usr/local/jboss-3.2.2/server/default/deploy/webapps/axis.war/WEB-INF/lib/wsdl4j.jar:/usr/local/jboss-3.2.2/server/default/deploy/webapps/axis.war/WEB-INF/lib/xmlsec.jar:/usr/local/j2sdk1.4.1_01/jre/lib/rt.jar:/usr/local/j2sdk1.4.1_01/jre/lib/i18n.jar:/usr/local/j2sdk1.4.1_01/jre/lib/sunrsasign.jar:/usr/local/j2sdk1.4.1_01/jre/lib/jsse.jar:/usr/local/j2sdk1.4.1_01/jre/lib/jce.jar:/usr/local/j2sdk1.4.1_01/jre/lib/charsets.jar:/usr/local/j2sdk1.4.1_01/jre/classes.


I don't recognise any servlet.jar or j2ee.jar in here that holds the HttpServletRequest definition ... I guess that the default classpath of msgContext is not good enough :-(.
What should I do?


Regards, Jan


Jan Kester wrote:


Hello

I am using jboss-3.2.2 with tomcat 4.1.27 integrated. I got the final axis 1.1 release, and deployed the webapps/axis directory under deploy/webapps/axis.war.
The happy axis page works, but the EchoHeaders.jws?wsdl fails as the axis compiler complains that it cannot compile the jws headers as HttpServletRequest is not found. I assume that the HttpServletRequest should be available on the jboss platform as normal jsp pages do compile. Only, it seems that the axis jws compiler does not have access to it ...


What should I do to get it working?

Regards, Jan




Reply via email to