Weird problem

[sa...@usbank.com]

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: 0x18) was found in the element content
of the
 document.

In the TCPTunnelGUI tool it displays the following

<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV
="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi
="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd
="http://www.w3.org/2001/XMLSchema">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>COMProvider: native code exception:[SOAPException:
faultCode=SOAP-ENV:Server; msg=Failed to get dispid for method
get_ServerName]</faultstring>
<faultactor>/webapp/soap/servlet/rpcrouter</faultactor>
</SOAP-ENV:Fault>

As you can see there is an illegal character at the end of the
"get_ServerName" method (The get_ServerName method returns a string)but I
don't know where it is coming from.
The getServerName method looks good to me in the DeploymentDescriptor as
well as in the client code. In fact I checked that using a hex editor.
Where else should I look to check this problem?

I am using the Xerces parser that comes with the
WSTK2.4 toolkit. I am able to run the com soap
examples the come with wstk2.4 without any problems...
Infact I am using the same xerces parser for my Websphere3.5 server too..
I am using the WindowsNT environment.

I was looking at soap-user archives and soap-dev archives and I found that
there are a few users who have got the exception regarding illegal
characters.. but there are no responses to them.
I was wondering if anyone was able to figure this problem out..or atleast
if there are any thoughts comments about it?


Thanx
Santosh