Good to hear you conquered the problem. I just downloaded 4.0.1 the other
day and was interested to see the things that changed, such as the libs
already in the path ready for servlets to use, and the "standards" for where
to put shared code. It's nice to not toy with the startup scripts at all.
Hi,
I am using Websphere3.5 and I am using the WSTK2.4 toolkit for generating
the Deployment descriptor files.
When I run my client code from the command prompt I get the following
error.
Caught SOAPException (SOAP-ENV:Client): Parsing error, response was:
An invalid XML character (Unicode: 0x
Now I send the string from the VB client to the Apache service via Literal
encoding(change the WSDL->Operation->Use from encoded to literal ). At the
service side, I changed the DeploymentDescriptor to use the
XMLParameterSerializer to be the deserializer of the large input String
parameter s4(pls
