axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject RE: [jira] Commented: (AXISCPP-794) Call class needs to return XML before deserializing
Date Fri, 12 Aug 2005 06:00:22 GMT

Hi Samisa,

I verified, I am using version 1.5. Please find AxisClient & XmlParser
dlls in the attachment. Version tab shows file versions as 1.5.0. I will
try to check out files from CVS.

Thanks & regards,


-----Original Message-----
From: Samisa Abeysinghe (JIRA) []
Sent: Friday, August 12, 2005 9:31 AM
To: Linesh Mahadik (WT01 - HLS)
Subject: [jira] Commented: (AXISCPP-794) Call class needs to return XML
before deserializing

318574 ]

Samisa Abeysinghe commented on AXISCPP-794:

BTW you seem to be using 1.3 release which is quite old.

Please use 1.5, or better use a CVS checkout.

> Call class needs to return XML before deserializing
> ---------------------------------------------------
>          Key: AXISCPP-794
>          URL:
>      Project: Axis-C++
>         Type: Improvement
>   Components: Client - Deserialization
>  Environment: Axis 1.3
> Xerces 2.6.0
>     Reporter: Linesh Mahadik

> Call class currently doesn't have any method to return undeserialized
> XML. In order to read XML response from a webservice, it currently
> expects the user to call following functions  if (TRUE =
CheckMessage("MessageName", NamespaceUrl)) {
>       string str = m_pCall->getElementAsString("elementName",
> NamespaceUrl) } This creates a requirement of having atleast 2 levels
> of XML nodes inside SOAP-BODY.
>     <MessageName>
>         <ElementName>
>             &lt;MyData/&gt;
>          </ElementName>
>     </MessageName>
> In case, the "ElementName" node in above XML is not sent or sent using
character entities ("&lt;" and "&gt;") it fails to deserialize that
> Providing a method to return entire incoming XML as a string or
through pointer to deserializer (SOapDeserializer *m_pIWSDZ) will enable
the user to implement custom deserializing.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

Confidentiality Notice

The information contained in this electronic message and any attachments to this message are
for the exclusive use of the addressee(s) and may contain confidential or privileged information.
you are not the intended recipient, please notify the sender at Wipro or
and destroy all copies of this message and any attachments.

View raw message