You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2010/10/01 18:00:39 UTC
[jira] Resolved: (CXF-3008) Consider adding a SAAJ frontend
[ 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.