Paolo,

Thakns for your input, as I have hoped the same -- figured that
just because Axis does not recognize a service is at Calculator.jws
when visiting it through the web, as long as its WSDL is available
everything should work fine.  However, here is what I have tried and
the results of each attempt.  Does anyone have any ideas what is
going on??

I really appreciate the help, as this is very important and bothersome
to me.

Just to reiterate, I'm using Tomcat 4.2.12 with Axis 1.0 on Redhat 8.0.
Tomcat works fine, everything tests OK.  Axis tests OK (happyaxis.jsp).

Here's what I got while testing CalcClient after I dropped Calculator.jws
into axis directory:

[root@mdf161 xml-axis-10]# java samples.userguide.example2.CalcClient -p8080
add 2 5
Exception in thread "main" java.lang.NoClassDefFoundError:
javax/servlet/ServletContext
        at java.lang.Class.getDeclaredMethods0(Native Method)
        at java.lang.Class.privateGetDeclaredMethods(Class.java:1627)
        at java.lang.Class.getMethod0(Class.java:1746)
        at java.lang.Class.getDeclaredMethod(Class.java:1233)
        at
org.apache.commons.discovery.tools.ClassUtils.findPublicStaticMethod(ClassUt
ils.java:112)
        at
org.apache.axis.configuration.EngineConfigurationFactoryFinder.newFactory(En
gineConfigurationFactoryFinder.java:214)
        at
org.apache.axis.configuration.EngineConfigurationFactoryFinder.access$300(En
gineConfigurationFactoryFinder.java:92)
        at
org.apache.axis.configuration.EngineConfigurationFactoryFinder$1.run(EngineC
onfigurationFactoryFinder.java:179)
        at java.security.AccessController.doPrivileged(Native Method)
        at
org.apache.axis.configuration.EngineConfigurationFactoryFinder.newFactory(En
gineConfigurationFactoryFinder.java:148)
        at
org.apache.axis.configuration.EngineConfigurationFactoryFinder.newFactory(En
gineConfigurationFactoryFinder.java:204)
        at org.apache.axis.client.Service.<init>(Service.java:111)
        at samples.userguide.example2.CalcClient.main(CalcClient.java:89)
[root@mdf161 xml-axis-10]#

[root@mdf161 xml-axis-10]# java samples.userguide.example2.CalcClient -p8080
2 5
Usage: CalcClient <add|subtract> arg1 arg2
[root@mdf161 xml-axis-10]#

I appreciate any help anyone could give. ... I have a strong feeling that
you will all ask for my classpath, but I am in windows now and
forgot to copy it .. but, I can say that I have all the required jar files
as specified in the axis installation guide, and they are all located
in $AXIS_LIB which is set to $AXIS_HOME/webapps/lib on my system.  Once
again this is from memory, but trust me that I have them
all in there, and I'm using xerces 2.2.0's xercesImpl.jar and
xmlParserAPIs.jar.

Thanks,
M. Fecina ([EMAIL PROTECTED])


----- Original Message -----
From: "Paolo Paganotto" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 30, 2002 4:18 AM
Subject: Re: deploying a .jws file as a web service - problems


>
> > Hello,
> >
> > I am using Apache Axis 1.0 release with Tomcat 4.2.12.  Everything seems
> > tobe working fine except, when I try to deploy Calculator.java as
> > Calculator.jws in the appropriate directory, I get the following error
> > when trying to visit the .jws page through the web:
> >
> > AXIS error
> > No service is available at tihs URL
> >
> > However, when I do:
> >
> > http://mdf161.rh.psu.edu:8080/axis/Calculator.jws?wsdl, I get returned
> > to me the right
> > WSDL file.  What's going on?  How come Axis 1.0 doesn't recognize the
> > fact that the jws is running at
> > http://mdf161.rh.psu.edu:8080/axis/Calculator.jws?
>
>
> ==>Hi,
> in my humble opinion, I think that the Axis configuration you've arranged
is
> ok if you are able to see the wsdl file.
> Try the client in the samples.userguide.example2.CalcClient (or something
> like that) package, as you can read in the axis userguide at page 7 (JWS
> Files - Instant Deployment);
> Run the client this way: java samples.userguide.example2.CalcClient -p8080
> add 2 5
> if the classpath is correc, you should get "7" as result.
> If it happens so, the web service is ok.
>
>
>

Reply via email to