You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-user@axis.apache.org by "Percey, Michael (MED US)" <mi...@siemens.com> on 2006/02/02 22:16:11 UTC
Problem With Namespaces
I have a VB 6.0 Client UI that must communicate with a Websphere Soap
Server. I'm building a CPP DLL using Axis C++ 1.5 to translate the VB
request into a SOAP Request, forward that request to Websphere, receive the
corresponding response, translate and return that response to the VB Client.
Note that we've already integrated Axis Java 1.3 into our Java Swing client
and it is succesfully processing Requests/Responses with the same Websphere
Soap Server.
I have the DLL up and running, and it is serializing the VB Request and
forwarding that request on to the server. It turns out that the Websphere
Soap Server cannot deserialize the Axis C++ Soap message because of the
NameSpace definition that appears within each arguement element.
I've verified this problem and solution using TCPMon. An example follows:
<SOAP-ENV:Body>
<ns1:processFlatRequest
xmlns:ns1="http://service.ctk.se.soarian.siemens.com
<http://service.ctk.se.soarian.siemens.com> ">
<arg_0_1>
<ns2:action xmlns:ns2="http://dto.ctk.se.soarian.siemens.com"
<http://dto.ctk.se.soarian.siemens.com> >getMasterFileList</ns2:action>
<ns3:object xmlns:ns3="http://dto.ctk.se.soarian.siemens.com"
<http://dto.ctk.se.soarian.siemens.com> >MasterFile</ns3:object>
<ns4:parms xmlns:ns4="http://dto.ctk.se.soarian.siemens.com"
<http://dto.ctk.se.soarian.siemens.com> >NULL</ns4:parms>
<ns5:requestXML
xmlns:ns5="http://dto.ctk.se.soarian.siemens.com"
<http://dto.ctk.se.soarian.siemens.com> >NULL</ns5:requestXML>
<ns6:minorVersion
xmlns:ns6="http://dto.ctk.se.soarian.siemens.com"
<http://dto.ctk.se.soarian.siemens.com> >1</ns6:minorVersion>
</arg_0_1>
<arg_1_1 xsi:nil="true"></arg_1_1>
</ns1:processFlatRequest>
</SOAP-ENV:Body>
The namespace on the request is not a problem. Then namespace on the
arguement elements cause the following error to occur:
Cannot deserialize element action of bean
com.siemens.soarian.se.ctk.dto.WSRequestFlatDTO. Message being parsed:
So, to the question. Are there any options to turn off the usage of the
Namespaces. If not, can anybody give me an idea where I need to look in the
source to modify this myself.
Thanks - MikeP
-------------------------------------------------------------------------------
This message and any included attachments are from Siemens Medical Solutions
USA, Inc. and are intended only for the addressee(s).
The information contained herein may include trade secrets or privileged or
otherwise confidential information. Unauthorized review, forwarding, printing,
copying, distributing, or using such information is strictly prohibited and may
be unlawful. If you received this message in error, or have reason to believe
you are not authorized to receive it, please promptly delete this message and
notify the sender by e-mail with a copy to Central.SecurityOffice@shs.siemens.com
Thank you
Re: Problem With Namespaces
Posted by Adrian Dick <ad...@uk.ibm.com>.
Hi,
Are you in a position to try the latest Axis C++ 1.6 nightly build? As
there have been a number of namespace related fixes since 1.5.
Adrian
_______________________________________
Adrian Dick (adrian.dick@uk.ibm.com)
"Percey, Michael (MED US)" <mi...@siemens.com> wrote on 02/02/2006
21:16:11:
> I have a VB 6.0 Client UI that must communicate with a Websphere
> Soap Server. I'm building a CPP DLL using Axis C++ 1.5 to translate
> the VB request into a SOAP Request, forward that request to
> Websphere, receive the corresponding response, translate and return
> that response to the VB Client.
>
> Note that we've already integrated Axis Java 1.3 into our Java Swing
> client and it is succesfully processing Requests/Responses with the
> same Websphere Soap Server.
>
> I have the DLL up and running, and it is serializing the VB Request
> and forwarding that request on to the server. It turns out that the
> Websphere Soap Server cannot deserialize the Axis C++ Soap message
> because of the NameSpace definition that appears within each
> arguement element.
>
> I've verified this problem and solution using TCPMon. An example
follows:
>
> <SOAP-ENV:Body>
> <ns1:processFlatRequest xmlns:ns1="http://service.ctk.se.
> soarian.siemens.com">
> <arg_0_1>
> <ns2:action
xmlns:ns2="http://dto.ctk.se.soarian.siemens.com
> ">getMasterFileList</ns2:action>
> <ns3:object
xmlns:ns3="http://dto.ctk.se.soarian.siemens.com
> ">MasterFile</ns3:object>
> <ns4:parms
xmlns:ns4="http://dto.ctk.se.soarian.siemens.com
> ">NULL</ns4:parms>
> <ns5:requestXML xmlns:ns5="http://dto.ctk.se.soarian.
> siemens.com">NULL</ns5:requestXML>
> <ns6:minorVersion xmlns:ns6="http://dto.ctk.se.
> soarian.siemens.com">1</ns6:minorVersion>
> </arg_0_1>
> <arg_1_1 xsi:nil="true"></arg_1_1>
> </ns1:processFlatRequest>
> </SOAP-ENV:Body>
> The namespace on the request is not a problem. Then namespace on
> the arguement elements cause the following error to occur:
> Cannot deserialize element action of bean com.siemens.soarian.se.
> ctk.dto.WSRequestFlatDTO. Message being parsed:
> So, to the question. Are there any options to turn off the usage of
> the Namespaces. If not, can anybody give me an idea where I need to
> look in the source to modify this myself.
>
> Thanks - MikeP
>
>
>
-------------------------------------------------------------------------------
> This message and any included attachments are from Siemens Medical
Solutions
> USA, Inc. and are intended only for the addressee(s).
> The information contained herein may include trade secrets or privileged
or
> otherwise confidential information. Unauthorized review,
forwarding,printing,
> copying, distributing, or using such information is strictly
> prohibited and may
> be unlawful. If you received this message in error, or have reason to
believe
> you are not authorized to receive it, please promptly delete this message
and
> notify the sender by e-mail with a copy to Central.
> SecurityOffice@shs.siemens.com
>
> Thank you