works for me. just downloaded jboss-3.2.2, dropped axis.war into C:\jboss-3.2.2\server\default\deploy and tried http://localhost:8080/axis/EchoHeaders.jws?wsdl. works fine.
thanks, dims --- Jan Kester <[EMAIL PROTECTED]> wrote: > One step further. It seems that the i18n error message, or missing > resource is due to my es_ES setup of my system. I changed it to en_US > and it didn't come up with the same message. It still doesn't work as > how it works directly under tomcat. Whenever I call a ?wsdl , the return > page is empty. In the jboss logs I only see a call to Exit: > JWSHandler::invoke, but no further output, no wsdl :-(. > I called the test local endpoint and that works. I deployed the > SoapMonitor and it seems to work as well (at the least the applet comes up). > So, not working: the empty pages for the ?wsdl calls and some > localization problem for i18n ... > > Regards, Jan. > > Jan Kester wrote: > > > Thanks, > > > > I just got the latest cvs, added the activation.jar, mail.jar > > (mailapi.jar) and a servlet.jar (the one from tomcat 4.1.29) to the > > lib dir and ran the target "ant war". > > The created build/webapps/axis I put under the jboss deploy dir with > > the name webapps/axis.war. The jboss hot deploy succeeds, the index > > and happy-axis pages work, but the wsdl call on > > axis/EchoHeaders.jws?wsdl fails with a new message now: > > > > > > AXIS error > > > > Sorry, something seems to have gone wrong... here are the details: > > > > Exception - java.lang.reflect.InvocationTargetException > > > > > > > > AXIS error > > > > Sorry, something seems to have gone wrong... here are the details: > > > > Exception - java.util.MissingResourceException: Can't find resource > > for bundle org.apache.axis.i18n.ProjectResourceBundle, key noService10 > > > > > > > > I try to work with defaults/standards as much as possible but I may be > > missing something? > > > > Regards, Jan. > > > > Davanum Srinivas wrote: > > > >> Just checked in a fix...Please try latest cvs. > >> > >> Thanks, > >> dims > >> > >> --- Jan Kester <[EMAIL PROTECTED]> wrote: > >> > >> > >>> 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 > >>>> > >>>> > >>>> > >>> > >>> > >> > >> > >> > >> ===== > >> Davanum Srinivas - http://webservices.apache.org/~dims/ > >> > >> > >> > > > > > > > > ===== Davanum Srinivas - http://webservices.apache.org/~dims/
