Thanks for the hint. But, my problem remains. Let me enumerate the exact steps I'm
taking so you can tell me if i'm missing something:
C:\blah\% del $TOMCAT_DIR$\webapps\axis\WEB-INF\server-config.wsdd
C:\blah\% javac foo\FooService.java
C:\blah\% copy foo\FooService.class $TOMCAT_DIR$\webapps\axis\WEB-INF\classes\foo\
C:\blah\% cd foo
C:\blah\% java org.apache.axis.client.AdminClient undeploy.wsdd
C:\blah\% java org.apache.axis.client.AdminClient deploy.wsdd
This all looks ok but when I attempt to invoke the service remotely, I get a
"NoSuchMethodException: pivotAction tried class: foo.FooService, method name
pivotAction". By the way it's document-style, so the method name I specify
(pivotAction) in my wsdl file (which corresponds to the method name in the
FooService.java) is arbitrary but should be ok.
Now the reason I think I have a versioning problem is that I used to deploy this
service with the method name "echoElements".
If I change the wsdd and java file method back to "echoElements", and redeploy using
the same steps, then when I run I get:
successful request and response!
However if I change the wsdd and java file method to another name "aaa", and redeploy
using the same steps, then when I run I get:
NoSuchMethodException: aaa
What's going on?
> > Do you know if any of this information is... cached in memory?
> > I'm just trying to figure out why the generated WSDL is inaccurate (has the method
>name from an old compilation) even though I run the updated deploy.wsdd file again.
>(I thought I already learned about the correct location to deploy updated classfiles
>so I'm HOPING that's not the problem ;) )
>
> You may try to undeploy the info.
>
> What I do when I changed the wsdd file, and forgot to undeploy it is to delete the
>file in $TOMCAT_DIR/webapps/axis/WEB-INF/server-config.wsdd
> I then redeploy all of my web services.
>
> I have a makefile to do this, so I just type, "make deploy". <g>
>
