axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nadir Amra <a...@us.ibm.com>
Subject Re: AxisIOStream vs SoapTransport
Date Tue, 15 Aug 2006 03:34:00 GMT
I would suggest you open a JIRA with this improvement request - it is 
legitimate and will be looked at....

Nadir K. Amra


Kamlesh kumar <kamaal79@yahoo.com> wrote on 08/14/2006 11:51:25 AM:

> I have created a very simple subtype of AxisIOStream
> using std::stringstream.
> 
> However, the SoapDeSerializer and SoapSerializer api
> for setting the input stream takes a SOAPTransport
> instead of AxisIOStream. 
> 
> int setInputStream(SOAPTransport* pInputStream);
> 
> Can anyone tell me why does it take a SOAPTransport
> and not a AxisIOStream ? 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. Let
> me know if this is feasible or not ? 
> 
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org


Mime
View raw message