[jbossws-issues] [JBoss JIRA] (JBWS-3901) Allow configuring default HTTP Conduit

[Alessio Soldano (JIRA)]

    [ https://issues.jboss.org/browse/JBWS-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055455#comment-13055455 ] 

Alessio Soldano commented on JBWS-3901:
---------------------------------------

Note: this will require an entry in the migration guide as the org.jboss.security.ignoreHttpsHost property is not used by jbossws-cxf anymore, while cxf.tls-client.disableCNCheck is used instead.

> Allow configuring default HTTP Conduit
> --------------------------------------
>
>                 Key: JBWS-3901
>                 URL: https://issues.jboss.org/browse/JBWS-3901
>             Project: JBoss Web Services
>          Issue Type: Feature Request
>          Components: jbossws-cxf
>            Reporter: Alessio Soldano
>            Assignee: Alessio Soldano
>             Fix For: jbossws-cxf-5.0
>
>
> With the Spring integration being deprecated, it's becoming even more important to allow users to easily set up the most common parameters in the CXF HTTP Conduit. Those include options fof HTTP chunking configuration as well as TLS/SSL options.
> We could have a wrapper of org.apache.cxf.transport.http.HTTPConduitFactory installed into each Bus that's build using the JBossWSBusFactory. That would configure any bus with proper defaults; it would get the values for the most common options through system properties.
> Moreover, we could use the usual Service API (META-INF/services/org.jboss.ws.cxf.transport.http.HTTPConduitFactoryWrapper or such) for resolving optional user provided conduit factory wrappers, to override the default behaviour.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)