[
https://issues.apache.org/jira/browse/AXISCPP-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra updated AXISCPP-992:
-------------------------------
Component/s: Client - API
> AxisIOStream vs SoapTransport ( Removing transport specific stuff from
> SoapSerializer and SoapDeSerializer)
> -----------------------------------------------------------------------------------------------------------
>
> Key: AXISCPP-992
> URL: https://issues.apache.org/jira/browse/AXISCPP-992
> Project: Axis-C++
> Issue Type: Improvement
> Components: Basic Architecture
> Reporter: kamlesh
>
> The SoapDeSerializer and SoapSerializer api
> for setting the stream takes a SOAPTransport
> instead of AxisIOStream.
> For ex:
> int setInputStream(SOAPTransport* pInputStream);
>
> Could it be refactored to take a AxisIOStream instead ?
> It would be nice if the transport specific stuff is handled outside of the
> serializer and deserializer in a separate class. This would allow anyone to
> easily implement a sub-type of AxisIOStream and pass it to the serializer and
> deserialer( for instance I have a custom AxisIOStream based on stringstream,
> however I can't use it since the serializer and deserializer take a
> SoapTransport)
> Let me know if this is feasible or not ?
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
