Pavel, I've looked into this some and see it as an opportunity to work in some other HTTP transport changes. I should have some changes ready in a day or two. I am thinking that a "getEnvelopeString" might end up working better on SOAPContext than SOAPTransport, but my foresight when coding is not perfect!
Scott Nichol ----- Original Message ----- From: "Pavel Ausianik" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, November 11, 2002 12:31 PM Subject: RE: SOAPTransport.receive() > Scott, > > recieve() currently defined in interface + implemented in 3 classes (Filter, > SMTP, HTTP transports) and directly used only in Message (result is not > stored), in Call used like follows: > > in = st.receive(); > payloadStr = IOUtils.getStringFromReader(in); > > To do not break compatibility we can add a method recieveString() to > transports, and implement recieve() method creating BufferedReader on demand > from stored String > > Pavel > > -- > To unsubscribe, e-mail: <mailto:soap-dev-unsubscribe@;xml.apache.org> > For additional commands, e-mail: <mailto:soap-dev-help@;xml.apache.org> > > -- To unsubscribe, e-mail: <mailto:soap-dev-unsubscribe@;xml.apache.org> For additional commands, e-mail: <mailto:soap-dev-help@;xml.apache.org>
