You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Linesh Mahadik (JIRA)" <ax...@ws.apache.org> on 2005/08/11 14:51:11 UTC
[jira] Created: (AXISCPP-794) Call class needs to return XML before deserializing
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
[jira] Commented: (AXISCPP-794) Call class needs to return XML before deserializing
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-794?page=comments#action_12318573 ]
Samisa Abeysinghe commented on AXISCPP-794:
-------------------------------------------
I am not sure if it would be possible to return the whole XML message to the Call class without deserailizing. This is because of the Pull model we are using.
If we are to do this change, we would have to change too many things in the current model as per my understanding. Because the parser, transport and the deserializer have tight relationships
The solution would be for you to overrride the SoapDeserializer and add whatever custom deserialization there.
> 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
[jira] Commented: (AXISCPP-794) Call class needs to return XML before deserializing
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-794?page=comments#action_12318574 ]
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: 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
[jira] Commented: (AXISCPP-794) Call class needs to return XML before deserializing
Posted by "Chinthana Danapala (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-794?page=comments#action_12318572 ]
Chinthana Danapala commented on AXISCPP-794:
--------------------------------------------
Hi Linesh,
Are you using Axis C++ 1.3 version? If so can you try this with 1.5 versions or you can get 1.6 latest codes from CVS and build and check with that.
Otherwise can you attach the WSDL file and client implementation?
> 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
[jira] Commented: (AXISCPP-794) Call class needs to return XML before deserializing
Posted by "John Hawkins (JIRA)" <ax...@ws.apache.org>.
[ 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
[jira] Closed: (AXISCPP-794) Call class needs to return XML before
deserializing
Posted by "nadir amra (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXISCPP-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
nadir amra closed AXISCPP-794.
------------------------------
Resolution: Not A Problem
> Call class needs to return XML before deserializing
> ---------------------------------------------------
>
> Key: AXISCPP-794
> URL: https://issues.apache.org/jira/browse/AXISCPP-794
> Project: Axis-C++
> Issue 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.
-
You can reply to this email to add a comment to the issue online.