[ http://issues.apache.org/jira/browse/AXISCPP-794?page=comments#action_12318607 ]
John Hawkins commented on AXISCPP-794: -------------------------------------- I noted some time ago that the serialiser interfaces are not exposed as seperate libraries - do we think this might be a good idea? > Call class needs to return XML before deserializing > --------------------------------------------------- > > Key: AXISCPP-794 > URL: http://issues.apache.org/jira/browse/AXISCPP-794 > 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. > <SOAP-BODY> > <MessageName> > <ElementName> > <MyData/> > </ElementName> > </MessageName> > </SOAP-BODY> > In case, the "ElementName" node in above XML is not sent or sent using > character entities ("<" and ">") it fails to deserialize that data. > 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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
