15-Oct-2005

SOAP again
Could set up the environment on Diana as on the client's machine, but where deployment was no problem at the clients's site, here an old error turned up again:

$ java "org.apache.axis.client.AdminClient" "deploy.wsdd"
Exception in thread "main" java.lang.NoClassDefFoundError:
org/w3c/dom/ranges/DocumentRange
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java)
...

Could it be some .jar missing in JAVA$CLASSPATH? Probably not, since I used EXACTLY the same setting as on the client site....
What was done at the customer site that the error didn't show up there? Could it be that building AXIS prevented the problem to occur? I don't like the idea of rebuilding AXIS on Diana usiang ant (remember the page-file issues????) but perhaps i just have to.
Luckylu no: There is no need to rebuild. Location from where deployment is done, matters:

$ set def ws:[000000]
$! this os where all webservice files are located, including deply script
$ java "org.apache.axis.client.AdminClient" "deploy.wsdd"
Exception in thread "main" java.lang.NoClassDefFoundError:
org/w3c/dom/ranges/DocumentRange
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java)

fails, but:

$ set def sys$login
$ set def [.services.ws] ! the same place as set def ws:[000000]
$ java "org.apache.axis.client.AdminClient" "deploy.wsdd"
Processing file deploy.wsdd
Done processing$
$

succeeds. Who explains???
However, as on the customer's site, the service doesn't show up in Axis's Show Services.

But compiling the webservice itself had no problem shown up here! One good thing, for a change.

(to be continued)