cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CXF-3008) Consider adding a SAAJ frontend
Date Fri, 01 Oct 2010 16:00:39 GMT

     [ https://issues.apache.org/jira/browse/CXF-3008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sergey Beryozkin resolved CXF-3008.
-----------------------------------

    Resolution: Won't Fix

> Consider adding a SAAJ frontend
> -------------------------------
>
>                 Key: CXF-3008
>                 URL: https://issues.apache.org/jira/browse/CXF-3008
>             Project: CXF
>          Issue Type: New Feature
>            Reporter: Sergey Beryozkin
>         Attachments: saaj.diff
>
>
> Some users use javax.xml.ws.SOAPConnection as a client side (frontend) api for consuming
SOAP web services.
> By providing a basic SAAJ frontend, CXF can help such users with configuring various
connection properties via using HTTP-aware conduits.
> Ex, the following fragment :
> SOAPConnectionFactory factory =  SOAPConnectionFactory.newInstance();
> SOAPConnection connection = factory.createConnection();
> SOAPMessage msg = MessageFactory.createMessage();
> // set up the message
> msg.getMimeHeaders().addHeader("Transfer-Encoding", "disabled");
> connection.call(msg, someAddress);
> can be used to disable the (chunked) transfer encoding.
> In this example, "disabled" is not a standard value - is an extension.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message