[
https://issues.apache.org/jira/browse/CXF-7840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16620580#comment-16620580
]
James Bailey commented on CXF-7840:
-----------------------------------
Weird. I'm sure I tried that during my investigations and it didn't work but
you are correct, changing the order of the code did fix the problem. I must
have had another problem that I subsequently fixed.
Thanks.
James Bailey
> TLSClientParameters are erased when changing the endpoint address
> -----------------------------------------------------------------
>
> Key: CXF-7840
> URL: https://issues.apache.org/jira/browse/CXF-7840
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 3.2.4, 3.2.6
> Environment: Windows/Windows server. CXF 3.2.4. Java 1.8.
> Reporter: James Bailey
> Assignee: Freeman Fang
> Priority: Major
> Attachments: CXFTLSTestCase.zip
>
>
> I have a set of WSDLs that I cannot change. They do not have the correct
> endpoint address for the server but that is easily changed by using
> provider.getRequestContext.put(ENDPOINT_ADDRESS_PROPERTY...
> This works fine as long as the server is not using a self signed certificate.
> But when I add the code to trust the certificate and also change the endpoint
> address, the TLSClientParameters are ignored because the conduit is
> reconfigured and replaced with a new conduit without the parameters. If I run
> once in a try block and then update the conduit with the TLSClientParameters
> and run a second time, this works.
> I've included a test case to show the problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
