Hi All,
it is good to see that some of us are making progress in getting Apache SOAP
2.2 up and running. For myself I'm not so lucky. From the many emails that
have been flying around I gather it most likely has something to do with
parser version conflicts.
My current settings are that I'm running Tomcat 3.2.3, Apache 1.4.2 . I have
pretty much renamed all occurences of the parser.jar and replaced them with
the latest Xerces parser where possible, xerces.jar is the first entry in my
classpath, the tomcat startup.bat has been edited to have xerces.jar the
first that gets added, etc, etc.
Still no luck - the AbstractMethod error keeps popping up.
For the record all the other tests; the rpcrouter URL and the messagerouter
URLS, calling the admin and asking for deployed services, undeploy when
non-are deployed... it all works or seems to work.
My questions is if there is a way to completely isolate the jars that get
called when I start up the ServiceManagerClient [SMC]so I can now for a fact
which parsers and other files get called when I start up the SMC.
I'll keep plodding along until I've solved the problem
but thanks in advance for any help or suggestion you may have
that will make me a happy SOAPer :-)
Kind regards,
Raynier van Egmond
Vashon Island (WA).
USA
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
