[ 
https://issues.apache.org/jira/browse/CONNECTORS-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888581#comment-16888581
 ] 

Karl Wright commented on CONNECTORS-1566:
-----------------------------------------

The TLSClientParameters programmatic way of setting things is still mysterious. 
 I see some examples online here:

https://www.programcreek.com/java-api-examples/?api=org.apache.cxf.configuration.jsse.TLSClientParameters

This looks promising because TLSClientParameters does have a way of setting a 
SSLSocketFactory, so if we can get this to be used for the construction of the 
service, we are over the hump.  But somehow we have to get hold of a 
org.apache.cxf.endpoint.Client object in order to be able to apply 
TLSClientParameters to it.  But it seems like this, too, requires an 
already-constructed service in order to work:

https://www.programcreek.com/java-api-examples/?api=org.apache.cxf.endpoint.Client

So this way is blocked too.

The only way this could really work in a non-static way is via a "Feature".  
The service constructors that CXF generates have options for including a list 
of Feature objects.  I do not know what Features are implemented by the JDK's 
transport but maybe somebody knows?




> Develop CSWS connector as a replacement for deprecated LiveLink LAPI connector
> ------------------------------------------------------------------------------
>
>                 Key: CONNECTORS-1566
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1566
>             Project: ManifoldCF
>          Issue Type: Task
>          Components: LiveLink connector
>    Affects Versions: ManifoldCF 2.12
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>            Priority: Major
>             Fix For: ManifoldCF 2.14
>
>         Attachments: OTCS_IIS.png, OTCS_Tomcat.png, chrome_cgfC00ujx7.png
>
>
> LAPI is being deprecated.  We need to develop a replacement for it using the 
> ContentServer Web Services API.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to