Thanks Dan for the clarifications...
Here's an initial attempt at providing a basic (client side) SAAJ frontend.
https://issues.apache.org/jira/browse/CXF-3008
It consists of 2 classes only, of which only SOAPConnectionImpl tries to do
anything useful.
Ex, it can be used to disable the chunked
On Monday 27 September 2010 2:04:02 pm Sergey Beryozkin wrote:
Thanks Dan for the clarifications...
Here's an initial attempt at providing a basic (client side) SAAJ frontend.
https://issues.apache.org/jira/browse/CXF-3008
It consists of 2 classes only, of which only SOAPConnectionImpl
Hi
On Mon, Sep 27, 2010 at 10:06 PM, Daniel Kulp dk...@apache.org wrote:
On Monday 27 September 2010 2:04:02 pm Sergey Beryozkin wrote:
Thanks Dan for the clarifications...
Here's an initial attempt at providing a basic (client side) SAAJ
frontend.
On Monday 27 September 2010 5:24:32 pm Sergey Beryozkin wrote:
I've proposed using DispatchSOAPMessage, but apparently, that was not an
option. I don't have more information.
I guess one possible reason they use SOAPConnection is that no service
QName is needed, may be for simple tests, etc.
Hi
I'm investigating the possibility of disabling the chunked encoding via the
use of opaque or (CXF) specific properties, set on a SOAPMessage
instance and posted via a SOAPConnection.
The idea is that users which may have to deal with multiple SOAP stacks (ex,
supported by a given provider),
