[jira] [Commented] (CXF-7953) make corba binding working with JDK11
[ https://issues.apache.org/jira/browse/CXF-7953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16812979#comment-16812979 ] Freeman Fang commented on CXF-7953: --- Hi [~dkulp], Yup, your commit works perfectly. Now we don't need to change the maven for the CI build machine. Thanks! Freeman > make corba binding working with JDK11 > - > > Key: CXF-7953 > URL: https://issues.apache.org/jira/browse/CXF-7953 > Project: CXF > Issue Type: Wish >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Minor > Fix For: 3.3.2 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CXF-7953) make corba binding working with JDK11
[ https://issues.apache.org/jira/browse/CXF-7953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16812856#comment-16812856 ] Freeman Fang commented on CXF-7953: --- [~dkulp] Ah, good idea. I will try that way. Cheers Freeman > make corba binding working with JDK11 > - > > Key: CXF-7953 > URL: https://issues.apache.org/jira/browse/CXF-7953 > Project: CXF > Issue Type: Wish >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Minor > Fix For: 3.3.2 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CXF-7953) make corba binding working with JDK11
[ https://issues.apache.org/jira/browse/CXF-7953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16812849#comment-16812849 ] Daniel Kulp commented on CXF-7953: -- Or we can do what I did and and the -npa flag to the xjc plugin to have it NOT generate the package-info.java and instead fully populate all the annotations. :) > make corba binding working with JDK11 > - > > Key: CXF-7953 > URL: https://issues.apache.org/jira/browse/CXF-7953 > Project: CXF > Issue Type: Wish >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Minor > Fix For: 3.3.2 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CXF-8014) Deserializing SOAP response with ~4K small objects is taking 1-2 mins
[
https://issues.apache.org/jira/browse/CXF-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Wells updated CXF-8014:
-
Description:
I'm hoping that this is the right place to report this, but apologies if not.
For a number of years now I've been using CXF in my product as a WSDL-generated
SOAP client. Everything works really, really well. In the past week I've seen a
situation with a particular end user where deserialization of a SOAP response
that contains a list of ~4K small objects is taking 1-2 minutes. I've updated
to 3.3.1 hoping that would resolve the issue, but it still remains. I know (or
at least strongly suspect) that it's happening in deserialization because I'm
logging immediately before and after the SOAP call from the perspective of the
calling client, and I've turned on in/out logging interceptors. Basically I see
the following in the log (with sensitive info redacted):
2019-04-07 23:18:38,364 [ 20299] DEBUG - ij.builder.ForceComBuilderUtil -
Before listMetadata() call.
2019-04-07 23:18:38,366 [ 20301] INFO - ervice.MetadataApi.MetadataApi -
Outbound Message
... Details removed
2019-04-07 23:18:51,613 [ 33548] INFO - ervice.MetadataApi.MetadataApi -
Inbound Message
... Details removed
... ~1m30s pause before returning to the caller
2019-04-07 23:20:20,095 [ 122030] DEBUG - ij.builder.ForceComBuilderUtil -
After listMetadata() call.
2019-04-07 23:20:20,095 [ 122030] DEBUG - ij.builder.ForceComBuilderUtil -
listMetadata() returned 4299 results.
I've tried to reproduce this behavior, but so far unsuccessfully. I have an
environment that includes about half this number of results, and the same call
takes ~2-3 seconds end-to-end.
Any idea what might be going on or how to get to the bottom of the issue?
Again, if this belongs somewhere else please just let me know, and thanks in
advance for the assistance.
was:
I'm hoping that this is the right place to report this, but apologies if not.
For a number of years now I've been using CXF in my product as a WSDL-generated
SOAP client. Everything works really, really well. In the past week I've seen a
situation with a particular end user where deserialization of a SOAP response
that contains a list of ~4K small objects is taking 1-2 minutes. I've updated
to 3.3.1 hoping that would resolve the issue, but it still remains. I know (or
at least strongly suspect) that it's happening in deserialization because I'm
logging immediately before and after the SOAP call from the perspective of the
calling client, and I've turned on in/out logging interceptors. Basically I see
the following in the log (with sensitive info redacted):
{{2019-04-07 23:18:38,364 [ 20299] DEBUG - ij.builder.ForceComBuilderUtil -
Before listMetadata() call.}}
{{ 2019-04-07 23:18:38,366 [ 20301] INFO - ervice.MetadataApi.MetadataApi -
Outbound Message}}
{{ ... Details removed}}
{{ 2019-04-07 23:18:51,613 [ 33548] INFO - ervice.MetadataApi.MetadataApi -
Inbound Message}}
{{ ... Details removed}}
{{ ... ~1m30s pause before returning to the caller}}
{{ 2019-04-07 23:20:20,095 [ 122030] DEBUG - ij.builder.ForceComBuilderUtil -
After listMetadata() call. }}
{{ 2019-04-07 23:20:20,095 [ 122030] DEBUG - ij.builder.ForceComBuilderUtil -
listMetadata() returned 4299 results.}}
I've tried to reproduce this behavior, but so far unsuccessfully. I have an
environment that includes about half this number of results, and the same call
takes ~2-3 seconds end-to-end.
Any idea what might be going on or how to get to the bottom of the issue?
Again, if this belongs somewhere else please just let me know, and thanks in
advance for the assistance.
> Deserializing SOAP response with ~4K small objects is taking 1-2 mins
> -
>
> Key: CXF-8014
> URL: https://issues.apache.org/jira/browse/CXF-8014
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
>Affects Versions: 3.3.1
>Reporter: Scott Wells
>Priority: Major
>
> I'm hoping that this is the right place to report this, but apologies if not.
> For a number of years now I've been using CXF in my product as a
> WSDL-generated SOAP client. Everything works really, really well. In the past
> week I've seen a situation with a particular end user where deserialization
> of a SOAP response that contains a list of ~4K small objects is taking 1-2
> minutes. I've updated to 3.3.1 hoping that would resolve the issue, but it
> still remains. I know (or at least strongly suspect) that it's happening in
> deserialization because I'm logging immediately before and after the SOAP
> call from the perspective of the calling client, and I've turned on in/out
> logging interceptors. Basically I see the following in the log (with
> sensitive info redacted):
> 2019-04-07 23:18:38,364 [ 20299]
[jira] [Updated] (CXF-8014) Deserializing SOAP response with ~4K small objects is taking 1-2 mins
[
https://issues.apache.org/jira/browse/CXF-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Wells updated CXF-8014:
-
Description:
I'm hoping that this is the right place to report this, but apologies if not.
For a number of years now I've been using CXF in my product as a WSDL-generated
SOAP client. Everything works really, really well. In the past week I've seen a
situation with a particular end user where deserialization of a SOAP response
that contains a list of ~4K small objects is taking 1-2 minutes. I've updated
to 3.3.1 hoping that would resolve the issue, but it still remains. I know (or
at least strongly suspect) that it's happening in deserialization because I'm
logging immediately before and after the SOAP call from the perspective of the
calling client, and I've turned on in/out logging interceptors. Basically I see
the following in the log (with sensitive info redacted):
{{2019-04-07 23:18:38,364 [ 20299] DEBUG - ij.builder.ForceComBuilderUtil -
Before listMetadata() call.}}
{{ 2019-04-07 23:18:38,366 [ 20301] INFO - ervice.MetadataApi.MetadataApi -
Outbound Message}}
{{ ... Details removed}}
{{ 2019-04-07 23:18:51,613 [ 33548] INFO - ervice.MetadataApi.MetadataApi -
Inbound Message}}
{{ ... Details removed}}
{{ ... ~1m30s pause before returning to the caller}}
{{ 2019-04-07 23:20:20,095 [ 122030] DEBUG - ij.builder.ForceComBuilderUtil -
After listMetadata() call. }}
{{ 2019-04-07 23:20:20,095 [ 122030] DEBUG - ij.builder.ForceComBuilderUtil -
listMetadata() returned 4299 results.}}
I've tried to reproduce this behavior, but so far unsuccessfully. I have an
environment that includes about half this number of results, and the same call
takes ~2-3 seconds end-to-end.
Any idea what might be going on or how to get to the bottom of the issue?
Again, if this belongs somewhere else please just let me know, and thanks in
advance for the assistance.
was:
I'm hoping that this is the right place to report this, but apologies if not.
For a number of years now I've been using CXF in my product as a WSDL-generated
SOAP client. Everything works really, really well. In the past week I've seen a
situation with a particular end user where deserialization of a SOAP response
that contains a list of ~4K small objects is taking 1-2 minutes. I've updated
to 3.3.1 hoping that would resolve the issue, but it still remains. I know (or
at least strongly suspect) that it's happening in deserialization because I'm
logging immediately before and after the SOAP call from the perspective of the
calling client, and I've turned on in/out logging interceptors. Basically I see
the following in the log (with sensitive info redacted):
{{2019-04-07 23:18:38,364 [ 20299] DEBUG - ij.builder.ForceComBuilderUtil -
Before listMetadata() call.
2019-04-07 23:18:38,366 [ 20301] INFO - ervice.MetadataApi.MetadataApi -
Outbound Message
... Details removed
2019-04-07 23:18:51,613 [ 33548] INFO - ervice.MetadataApi.MetadataApi -
Inbound Message
... Details removed
... ~1m30s pause before returning to the caller
2019-04-07 23:20:20,095 [ 122030] DEBUG - ij.builder.ForceComBuilderUtil -
After listMetadata() call.
2019-04-07 23:20:20,095 [ 122030] DEBUG - ij.builder.ForceComBuilderUtil -
listMetadata() returned 4299 results. }}
I've tried to reproduce this behavior, but so far unsuccessfully. I have an
environment that includes about half this number of results, and the same call
takes ~2-3 seconds end-to-end.
Any idea what might be going on or how to get to the bottom of the issue?
Again, if this belongs somewhere else please just let me know, and thanks in
advance for the assistance.
> Deserializing SOAP response with ~4K small objects is taking 1-2 mins
> -
>
> Key: CXF-8014
> URL: https://issues.apache.org/jira/browse/CXF-8014
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
>Affects Versions: 3.3.1
>Reporter: Scott Wells
>Priority: Major
>
> I'm hoping that this is the right place to report this, but apologies if not.
> For a number of years now I've been using CXF in my product as a
> WSDL-generated SOAP client. Everything works really, really well. In the past
> week I've seen a situation with a particular end user where deserialization
> of a SOAP response that contains a list of ~4K small objects is taking 1-2
> minutes. I've updated to 3.3.1 hoping that would resolve the issue, but it
> still remains. I know (or at least strongly suspect) that it's happening in
> deserialization because I'm logging immediately before and after the SOAP
> call from the perspective of the calling client, and I've turned on in/out
> logging interceptors. Basically I see the following in the log (with
> sensitive info redacted):
> {{2019-04-07 23:18:38,364 [
[jira] [Updated] (CXF-8014) Deserializing SOAP response with ~4K small objects is taking 1-2 mins
[
https://issues.apache.org/jira/browse/CXF-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Wells updated CXF-8014:
-
Description:
I'm hoping that this is the right place to report this, but apologies if not.
For a number of years now I've been using CXF in my product as a WSDL-generated
SOAP client. Everything works really, really well. In the past week I've seen a
situation with a particular end user where deserialization of a SOAP response
that contains a list of ~4K small objects is taking 1-2 minutes. I've updated
to 3.3.1 hoping that would resolve the issue, but it still remains. I know (or
at least strongly suspect) that it's happening in deserialization because I'm
logging immediately before and after the SOAP call from the perspective of the
calling client, and I've turned on in/out logging interceptors. Basically I see
the following in the log (with sensitive info redacted):
{{2019-04-07 23:18:38,364 [ 20299] DEBUG - ij.builder.ForceComBuilderUtil -
Before listMetadata() call.
2019-04-07 23:18:38,366 [ 20301] INFO - ervice.MetadataApi.MetadataApi -
Outbound Message
... Details removed
2019-04-07 23:18:51,613 [ 33548] INFO - ervice.MetadataApi.MetadataApi -
Inbound Message
... Details removed
... ~1m30s pause before returning to the caller
2019-04-07 23:20:20,095 [ 122030] DEBUG - ij.builder.ForceComBuilderUtil -
After listMetadata() call.
2019-04-07 23:20:20,095 [ 122030] DEBUG - ij.builder.ForceComBuilderUtil -
listMetadata() returned 4299 results. }}
I've tried to reproduce this behavior, but so far unsuccessfully. I have an
environment that includes about half this number of results, and the same call
takes ~2-3 seconds end-to-end.
Any idea what might be going on or how to get to the bottom of the issue?
Again, if this belongs somewhere else please just let me know, and thanks in
advance for the assistance.
was:
I'm hoping that this is the right place to report this, but apologies if not.
For a number of years now I've been using CXF in my product as a WSDL-generated
SOAP client. Everything works really, really well. In the past week I've seen a
situation with a particular end user where deserialization of a SOAP response
that contains a list of ~4K small objects is taking 1-2 minutes. I've updated
to 3.3.1 hoping that would resolve the issue, but it still remains. I know (or
at least strongly suspect) that it's happening in deserialization because I'm
logging immediately before and after the SOAP call from the perspective of the
calling client, and I've turned on in/out logging interceptors. Basically I see
the following in the log (with sensitive info redacted):
{{2019-04-07 23:18:38,364 [ 20299] DEBUG - ij.builder.ForceComBuilderUtil -
Before listMetadata() call. }}
{{2019-04-07 23:18:38,366 [ 20301] INFO - ervice.MetadataApi.MetadataApi -
Outbound Message}}
{{... Details removed}}
{{2019-04-07 23:18:51,613 [ 33548] INFO - ervice.MetadataApi.MetadataApi -
Inbound Message}}
{{... Details removed}}
{{... ~1m30s pause before returning to the caller}}
{{2019-04-07 23:20:20,095 [ 122030] DEBUG - ij.builder.ForceComBuilderUtil -
After listMetadata() call. }}
{{2019-04-07 23:20:20,095 [ 122030] DEBUG - ij.builder.ForceComBuilderUtil -
listMetadata() returned 4299 results. }}
I've tried to reproduce this behavior, but so far unsuccessfully. I have an
environment that includes about half this number of results, and the same call
takes ~2-3 seconds end-to-end.
Any idea what might be going on or how to get to the bottom of the issue?
Again, if this belongs somewhere else please just let me know, and thanks in
advance for the assistance.
> Deserializing SOAP response with ~4K small objects is taking 1-2 mins
> -
>
> Key: CXF-8014
> URL: https://issues.apache.org/jira/browse/CXF-8014
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
>Affects Versions: 3.3.1
>Reporter: Scott Wells
>Priority: Major
>
> I'm hoping that this is the right place to report this, but apologies if not.
> For a number of years now I've been using CXF in my product as a
> WSDL-generated SOAP client. Everything works really, really well. In the past
> week I've seen a situation with a particular end user where deserialization
> of a SOAP response that contains a list of ~4K small objects is taking 1-2
> minutes. I've updated to 3.3.1 hoping that would resolve the issue, but it
> still remains. I know (or at least strongly suspect) that it's happening in
> deserialization because I'm logging immediately before and after the SOAP
> call from the perspective of the calling client, and I've turned on in/out
> logging interceptors. Basically I see the following in the log (with
> sensitive info redacted):
> {{2019-04-07 23:18:38,364 [
[jira] [Created] (CXF-8014) Deserializing SOAP response with ~4K small objects is taking 1-2 mins
Scott Wells created CXF-8014:
Summary: Deserializing SOAP response with ~4K small objects is
taking 1-2 mins
Key: CXF-8014
URL: https://issues.apache.org/jira/browse/CXF-8014
Project: CXF
Issue Type: Bug
Components: JAX-WS Runtime
Affects Versions: 3.3.1
Reporter: Scott Wells
I'm hoping that this is the right place to report this, but apologies if not.
For a number of years now I've been using CXF in my product as a WSDL-generated
SOAP client. Everything works really, really well. In the past week I've seen a
situation with a particular end user where deserialization of a SOAP response
that contains a list of ~4K small objects is taking 1-2 minutes. I've updated
to 3.3.1 hoping that would resolve the issue, but it still remains. I know (or
at least strongly suspect) that it's happening in deserialization because I'm
logging immediately before and after the SOAP call from the perspective of the
calling client, and I've turned on in/out logging interceptors. Basically I see
the following in the log (with sensitive info redacted):
{{2019-04-07 23:18:38,364 [ 20299] DEBUG - ij.builder.ForceComBuilderUtil -
Before listMetadata() call. }}
{{2019-04-07 23:18:38,366 [ 20301] INFO - ervice.MetadataApi.MetadataApi -
Outbound Message}}
{{... Details removed}}
{{2019-04-07 23:18:51,613 [ 33548] INFO - ervice.MetadataApi.MetadataApi -
Inbound Message}}
{{... Details removed}}
{{... ~1m30s pause before returning to the caller}}
{{2019-04-07 23:20:20,095 [ 122030] DEBUG - ij.builder.ForceComBuilderUtil -
After listMetadata() call. }}
{{2019-04-07 23:20:20,095 [ 122030] DEBUG - ij.builder.ForceComBuilderUtil -
listMetadata() returned 4299 results. }}
I've tried to reproduce this behavior, but so far unsuccessfully. I have an
environment that includes about half this number of results, and the same call
takes ~2-3 seconds end-to-end.
Any idea what might be going on or how to get to the bottom of the issue?
Again, if this belongs somewhere else please just let me know, and thanks in
advance for the assistance.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CXF-8013) Can't tell CXF to use a custom certstore for SSL certificate check
[
https://issues.apache.org/jira/browse/CXF-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16812478#comment-16812478
]
Colm O hEigeartaigh commented on CXF-8013:
--
{code:java}
{code}
You want to use either certStore or keyStore here.
> Can't tell CXF to use a custom certstore for SSL certificate check
> --
>
> Key: CXF-8013
> URL: https://issues.apache.org/jira/browse/CXF-8013
> Project: CXF
> Issue Type: Bug
>Affects Versions: 3.1.6
>Reporter: Michel SAUMON
>Assignee: Freeman Fang
>Priority: Major
>
> In my cxf.xml, I declared a custom certstore because my server's certificate
> is not considered valid by the JDK:
> {code:java}
> http://www.springframework.org/schema/beans;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xmlns:sec="http://cxf.apache.org/configuration/security;
> xmlns:http="http://cxf.apache.org/transports/http/configuration;
> xmlns:jaxws="http://java.sun.com/xml/ns/jaxws;
> xsi:schemaLocation="
> http://cxf.apache.org/configuration/security
> http://cxf.apache.org/schemas/configuration/security.xsd
> http://cxf.apache.org/transports/http/configuration
> http://cxf.apache.org/schemas/configuration/http-conf.xsd
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.0.xsd;>
>
> http://myservice.xx/comweb/}ComWebSoap.http-conduit;>
>
>
>
>
>
>
>
>
>
>
> {code}
> But CXF does not take this config.
> I have still the error telling the cert is not valid :
> {code:java}
> javax.xml.ws.WebServiceException:
> org.apache.cxf.service.factory.ServiceConstructionException: Failed to create
> service.
> at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:163)
> at org.apache.cxf.jaxws.ServiceImpl.(ServiceImpl.java:129)
> at
> org.apache.cxf.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:82)
> at javax.xml.ws.Service.(Service.java:77)
> at xx.mysoapclient.ComWeb.(ComWeb.java:40)
> at xx.mysoapclient.ComWebTest.getComWebSoap(ComWebTest.java:101)
> at xx.mysoapclient.ComWebTest.testGetReporting(ComWebTest.java:136)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)
> Caused by: org.apache.cxf.service.factory.ServiceConstructionException:
> Failed to create service.
> at
> org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:87)
> at org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:218)
> at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:161)
> ... 25 more
> Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR:
> Problem parsing 'https://ctrl-talend-s95/COM_WEB/ComWeb.asmx?wsdl'.:
> javax.net.ssl.SSLHandshakeException:
> sun.security.validator.ValidatorException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target
> at com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(WSDLReaderImpl.java:2198)
> at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2390)
> at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2422)
> at
>
[jira] [Commented] (CXF-7953) make corba binding working with JDK11
[ https://issues.apache.org/jira/browse/CXF-7953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16812219#comment-16812219 ] Colm O hEigeartaigh commented on CXF-7953: -- [~ffang] (y) > make corba binding working with JDK11 > - > > Key: CXF-7953 > URL: https://issues.apache.org/jira/browse/CXF-7953 > Project: CXF > Issue Type: Wish >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Minor > Fix For: 3.3.2 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CXF-8013) Can't tell CXF to use a custom certstore for SSL certificate check
[
https://issues.apache.org/jira/browse/CXF-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang reassigned CXF-8013:
-
Assignee: Freeman Fang
> Can't tell CXF to use a custom certstore for SSL certificate check
> --
>
> Key: CXF-8013
> URL: https://issues.apache.org/jira/browse/CXF-8013
> Project: CXF
> Issue Type: Bug
>Affects Versions: 3.1.6
>Reporter: Michel SAUMON
>Assignee: Freeman Fang
>Priority: Major
>
> In my cxf.xml, I declared a custom certstore because my server's certificate
> is not considered valid by the JDK:
> {code:java}
> http://www.springframework.org/schema/beans;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xmlns:sec="http://cxf.apache.org/configuration/security;
> xmlns:http="http://cxf.apache.org/transports/http/configuration;
> xmlns:jaxws="http://java.sun.com/xml/ns/jaxws;
> xsi:schemaLocation="
> http://cxf.apache.org/configuration/security
> http://cxf.apache.org/schemas/configuration/security.xsd
> http://cxf.apache.org/transports/http/configuration
> http://cxf.apache.org/schemas/configuration/http-conf.xsd
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.0.xsd;>
>
> http://myservice.xx/comweb/}ComWebSoap.http-conduit;>
>
>
>
>
>
>
>
>
>
>
> {code}
> But CXF does not take this config.
> I have still the error telling the cert is not valid :
> {code:java}
> javax.xml.ws.WebServiceException:
> org.apache.cxf.service.factory.ServiceConstructionException: Failed to create
> service.
> at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:163)
> at org.apache.cxf.jaxws.ServiceImpl.(ServiceImpl.java:129)
> at
> org.apache.cxf.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:82)
> at javax.xml.ws.Service.(Service.java:77)
> at xx.mysoapclient.ComWeb.(ComWeb.java:40)
> at xx.mysoapclient.ComWebTest.getComWebSoap(ComWebTest.java:101)
> at xx.mysoapclient.ComWebTest.testGetReporting(ComWebTest.java:136)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)
> Caused by: org.apache.cxf.service.factory.ServiceConstructionException:
> Failed to create service.
> at
> org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:87)
> at org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:218)
> at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:161)
> ... 25 more
> Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR:
> Problem parsing 'https://ctrl-talend-s95/COM_WEB/ComWeb.asmx?wsdl'.:
> javax.net.ssl.SSLHandshakeException:
> sun.security.validator.ValidatorException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target
> at com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(WSDLReaderImpl.java:2198)
> at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2390)
> at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2422)
> at
> org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:238)
> at
>
[jira] [Comment Edited] (CXF-8013) Can't tell CXF to use a custom certstore for SSL certificate check
[
https://issues.apache.org/jira/browse/CXF-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16812198#comment-16812198
]
Freeman Fang edited comment on CXF-8013 at 4/8/19 7:53 AM:
---
Hi,
In your scenario you use https to retrieve the wsdl, so you [need read
this|http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html]
, more specifically, this part
{code}
If your service endpoint uses an SSL WSDL location (i.e., "https://xxx?wsdl;),
you can configure the http conduit to pick up the SSL configuration by using a
hardcoded http conduit name of
"{http://cxf.apache.org/}TransportURIResolver.http-conduit;
{code}
so the should be like
{code}
http://cxf.apache.org/}TransportURIResolver.http-conduit;>
{code}
Cheers
Freeman
was (Author: ffang):
Hi,
In your scenario you use https to retrieve the wsdl, so you [need read
this|http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html]
, more specifically, this part
{code}
If your service endpoint uses an SSL WSDL location (i.e., "https://xxx?wsdl;),
you can configure the http conduit to pick up the SSL configuration by using a
hardcoded http conduit name of
"{http://cxf.apache.org/}TransportURIResolver.http-conduit;
{code}
Freeman
> Can't tell CXF to use a custom certstore for SSL certificate check
> --
>
> Key: CXF-8013
> URL: https://issues.apache.org/jira/browse/CXF-8013
> Project: CXF
> Issue Type: Bug
>Affects Versions: 3.1.6
>Reporter: Michel SAUMON
>Priority: Major
>
> In my cxf.xml, I declared a custom certstore because my server's certificate
> is not considered valid by the JDK:
> {code:java}
> http://www.springframework.org/schema/beans;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xmlns:sec="http://cxf.apache.org/configuration/security;
> xmlns:http="http://cxf.apache.org/transports/http/configuration;
> xmlns:jaxws="http://java.sun.com/xml/ns/jaxws;
> xsi:schemaLocation="
> http://cxf.apache.org/configuration/security
> http://cxf.apache.org/schemas/configuration/security.xsd
> http://cxf.apache.org/transports/http/configuration
> http://cxf.apache.org/schemas/configuration/http-conf.xsd
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.0.xsd;>
>
> http://myservice.xx/comweb/}ComWebSoap.http-conduit;>
>
>
>
>
>
>
>
>
>
>
> {code}
> But CXF does not take this config.
> I have still the error telling the cert is not valid :
> {code:java}
> javax.xml.ws.WebServiceException:
> org.apache.cxf.service.factory.ServiceConstructionException: Failed to create
> service.
> at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:163)
> at org.apache.cxf.jaxws.ServiceImpl.(ServiceImpl.java:129)
> at
> org.apache.cxf.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:82)
> at javax.xml.ws.Service.(Service.java:77)
> at xx.mysoapclient.ComWeb.(ComWeb.java:40)
> at xx.mysoapclient.ComWebTest.getComWebSoap(ComWebTest.java:101)
> at xx.mysoapclient.ComWebTest.testGetReporting(ComWebTest.java:136)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)
> Caused by:
[jira] [Commented] (CXF-8013) Can't tell CXF to use a custom certstore for SSL certificate check
[
https://issues.apache.org/jira/browse/CXF-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16812198#comment-16812198
]
Freeman Fang commented on CXF-8013:
---
Hi,
In your scenario you use https to retrieve the wsdl, so you [need read
this|http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html]
, more specifically, this part
{code}
If your service endpoint uses an SSL WSDL location (i.e., "https://xxx?wsdl;),
you can configure the http conduit to pick up the SSL configuration by using a
hardcoded http conduit name of
"{http://cxf.apache.org/}TransportURIResolver.http-conduit;
{code}
Freeman
> Can't tell CXF to use a custom certstore for SSL certificate check
> --
>
> Key: CXF-8013
> URL: https://issues.apache.org/jira/browse/CXF-8013
> Project: CXF
> Issue Type: Bug
>Affects Versions: 3.1.6
>Reporter: Michel SAUMON
>Priority: Major
>
> In my cxf.xml, I declared a custom certstore because my server's certificate
> is not considered valid by the JDK:
> {code:java}
> http://www.springframework.org/schema/beans;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xmlns:sec="http://cxf.apache.org/configuration/security;
> xmlns:http="http://cxf.apache.org/transports/http/configuration;
> xmlns:jaxws="http://java.sun.com/xml/ns/jaxws;
> xsi:schemaLocation="
> http://cxf.apache.org/configuration/security
> http://cxf.apache.org/schemas/configuration/security.xsd
> http://cxf.apache.org/transports/http/configuration
> http://cxf.apache.org/schemas/configuration/http-conf.xsd
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.0.xsd;>
>
> http://myservice.xx/comweb/}ComWebSoap.http-conduit;>
>
>
>
>
>
>
>
>
>
>
> {code}
> But CXF does not take this config.
> I have still the error telling the cert is not valid :
> {code:java}
> javax.xml.ws.WebServiceException:
> org.apache.cxf.service.factory.ServiceConstructionException: Failed to create
> service.
> at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:163)
> at org.apache.cxf.jaxws.ServiceImpl.(ServiceImpl.java:129)
> at
> org.apache.cxf.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:82)
> at javax.xml.ws.Service.(Service.java:77)
> at xx.mysoapclient.ComWeb.(ComWeb.java:40)
> at xx.mysoapclient.ComWebTest.getComWebSoap(ComWebTest.java:101)
> at xx.mysoapclient.ComWebTest.testGetReporting(ComWebTest.java:136)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)
> Caused by: org.apache.cxf.service.factory.ServiceConstructionException:
> Failed to create service.
> at
> org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:87)
> at org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:218)
> at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:161)
> ... 25 more
> Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR:
> Problem parsing 'https://ctrl-talend-s95/COM_WEB/ComWeb.asmx?wsdl'.:
> javax.net.ssl.SSLHandshakeException:
> sun.security.validator.ValidatorException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException:
[jira] [Updated] (CXF-8013) Can't tell CXF to use a custom certstore for SSL certificate check
[
https://issues.apache.org/jira/browse/CXF-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michel SAUMON updated CXF-8013:
---
Description:
In my cxf.xml, I declared a custom certstore because my server's certificate is
not considered valid by the JDK:
{code:java}
http://www.springframework.org/schema/beans;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xmlns:sec="http://cxf.apache.org/configuration/security;
xmlns:http="http://cxf.apache.org/transports/http/configuration;
xmlns:jaxws="http://java.sun.com/xml/ns/jaxws;
xsi:schemaLocation="
http://cxf.apache.org/configuration/security
http://cxf.apache.org/schemas/configuration/security.xsd
http://cxf.apache.org/transports/http/configuration
http://cxf.apache.org/schemas/configuration/http-conf.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd;>
http://myservice.xx/comweb/}ComWebSoap.http-conduit;>
{code}
But CXF does not take this config.
I have still the error telling the cert is not valid :
{code:java}
javax.xml.ws.WebServiceException:
org.apache.cxf.service.factory.ServiceConstructionException: Failed to create
service.
at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:163)
at org.apache.cxf.jaxws.ServiceImpl.(ServiceImpl.java:129)
at
org.apache.cxf.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:82)
at javax.xml.ws.Service.(Service.java:77)
at xx.mysoapclient.ComWeb.(ComWeb.java:40)
at xx.mysoapclient.ComWebTest.getComWebSoap(ComWebTest.java:101)
at xx.mysoapclient.ComWebTest.testGetReporting(ComWebTest.java:136)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:252)
at junit.framework.TestSuite.run(TestSuite.java:247)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)
Caused by: org.apache.cxf.service.factory.ServiceConstructionException: Failed
to create service.
at
org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:87)
at org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:218)
at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:161)
... 25 more
Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR:
Problem parsing 'https://ctrl-talend-s95/COM_WEB/ComWeb.asmx?wsdl'.:
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException:
PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
at com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(WSDLReaderImpl.java:2198)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2390)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2422)
at
org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:238)
at
org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:163)
at
org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:85)
... 27 more
Caused by: javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
at
[jira] [Updated] (CXF-8013) Can't tell CXF to use a custom certstore for SSL certificate check
[
https://issues.apache.org/jira/browse/CXF-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michel SAUMON updated CXF-8013:
---
Description:
In my cxf.xml, I declared a custom certstore because my server's certificate is
not considered valid by the JDK:
{code:java}
http://www.springframework.org/schema/beans;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xmlns:sec="http://cxf.apache.org/configuration/security;
xmlns:http="http://cxf.apache.org/transports/http/configuration;
xmlns:jaxws="http://java.sun.com/xml/ns/jaxws;
xsi:schemaLocation="
http://cxf.apache.org/configuration/security
http://cxf.apache.org/schemas/configuration/security.xsd
http://cxf.apache.org/transports/http/configuration
http://cxf.apache.org/schemas/configuration/http-conf.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd;>
http://myservice.xx/comweb/}ComWebSoap.http-conduit;>
{code}
But CXF does not take this config.
I have still the error telling the cert is not valid :
{code:java}
javax.xml.ws.WebServiceException:
org.apache.cxf.service.factory.ServiceConstructionException: Failed to create
service.
at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:163)
at org.apache.cxf.jaxws.ServiceImpl.(ServiceImpl.java:129)
at
org.apache.cxf.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:82)
at javax.xml.ws.Service.(Service.java:77)
at com.sylob.cochise.myreport.ComWeb.(ComWeb.java:40)
at com.sylob.cochise.myreport.ComWebTest.getComWebSoap(ComWebTest.java:101)
at
com.sylob.cochise.myreport.ComWebTest.testGetReporting(ComWebTest.java:136)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:252)
at junit.framework.TestSuite.run(TestSuite.java:247)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)
Caused by: org.apache.cxf.service.factory.ServiceConstructionException: Failed
to create service.
at
org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:87)
at org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:218)
at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:161)
... 25 more
Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR:
Problem parsing 'https://ctrl-talend-s95/COM_WEB/ComWeb.asmx?wsdl'.:
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException:
PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
at com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(WSDLReaderImpl.java:2198)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2390)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2422)
at
org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:238)
at
org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:163)
at
org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:85)
... 27 more
Caused by: javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
at
[jira] [Updated] (CXF-8013) Can't tell CXF to use a custom certstore for SSL certificate check
[
https://issues.apache.org/jira/browse/CXF-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michel SAUMON updated CXF-8013:
---
Description:
In my cxf.xml, I declared a custom certstore because my server's certificate is
not considered valid by the JDK:
{code:java}
http://www.springframework.org/schema/beans;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xmlns:sec="http://cxf.apache.org/configuration/security;
xmlns:http="http://cxf.apache.org/transports/http/configuration;
xmlns:jaxws="http://java.sun.com/xml/ns/jaxws;
xsi:schemaLocation="
http://cxf.apache.org/configuration/security
http://cxf.apache.org/schemas/configuration/security.xsd
http://cxf.apache.org/transports/http/configuration
http://cxf.apache.org/schemas/configuration/http-conf.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd;>
http://myservice.xx/comweb/}ComWebSoap.http-conduit;>
{code}
But CXF does not take this config.
I have still the error telling the cert is not valid :
{code:java}
javax.xml.ws.WebServiceException:
org.apache.cxf.service.factory.ServiceConstructionException: Failed to create
service.
at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:163)
at org.apache.cxf.jaxws.ServiceImpl.(ServiceImpl.java:129)
at
org.apache.cxf.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:82)
at javax.xml.ws.Service.(Service.java:77)
at com.sylob.cochise.myreport.ComWeb.(ComWeb.java:40)
at com.sylob.cochise.myreport.ComWebTest.getComWebSoap(ComWebTest.java:101)
at
com.sylob.cochise.myreport.ComWebTest.testGetReporting(ComWebTest.java:136)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:252)
at junit.framework.TestSuite.run(TestSuite.java:247)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)
Caused by: org.apache.cxf.service.factory.ServiceConstructionException: Failed
to create service.
at
org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:87)
at org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:218)
at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:161)
... 25 more
Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR:
Problem parsing 'https://ctrl-talend-s95/COM_WEB/ComWeb.asmx?wsdl'.:
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException:
PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
at com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(WSDLReaderImpl.java:2198)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2390)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2422)
at
org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:238)
at
org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:163)
at
org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:85)
... 27 more
Caused by: javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
at
[jira] [Updated] (CXF-8013) Can't tell CXF to use a custom certstore for SSL certificate check
[
https://issues.apache.org/jira/browse/CXF-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michel SAUMON updated CXF-8013:
---
Description:
In my cxf.xml, I declared a custom certstore because my server's certificate is
not considered valid by the JDK:
{code:java}
http://www.springframework.org/schema/beans;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xmlns:sec="http://cxf.apache.org/configuration/security;
xmlns:http="http://cxf.apache.org/transports/http/configuration;
xmlns:jaxws="http://java.sun.com/xml/ns/jaxws;
xsi:schemaLocation="
http://cxf.apache.org/configuration/security
http://cxf.apache.org/schemas/configuration/security.xsd
http://cxf.apache.org/transports/http/configuration
http://cxf.apache.org/schemas/configuration/http-conf.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd;>
http://myservice.xx/comweb/}ComWebSoap.http-conduit;>
{code}
But CXF does not take this config.
I have still the error telling the cert is not valid :
{code:java}
javax.xml.ws.WebServiceException:
org.apache.cxf.service.factory.ServiceConstructionException: Failed to create
service.
at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:163)
at org.apache.cxf.jaxws.ServiceImpl.(ServiceImpl.java:129)
at
org.apache.cxf.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:82)
at javax.xml.ws.Service.(Service.java:77)
at com.sylob.cochise.myreport.ComWeb.(ComWeb.java:40)
at com.sylob.cochise.myreport.ComWebTest.getComWebSoap(ComWebTest.java:101)
at
com.sylob.cochise.myreport.ComWebTest.testGetReporting(ComWebTest.java:136)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:252)
at junit.framework.TestSuite.run(TestSuite.java:247)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)
Caused by: org.apache.cxf.service.factory.ServiceConstructionException: Failed
to create service.
at
org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:87)
at org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:218)
at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:161)
... 25 more
Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR:
Problem parsing 'https://ctrl-talend-s95/COM_WEB/ComWeb.asmx?wsdl'.:
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException:
PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
at com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(WSDLReaderImpl.java:2198)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2390)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2422)
at
org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:238)
at
org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:163)
at
org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:85)
... 27 more
Caused by: javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
at
[jira] [Updated] (CXF-8013) Can't tell CXF to use a custom certstore for SSL certificate check
[
https://issues.apache.org/jira/browse/CXF-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michel SAUMON updated CXF-8013:
---
Affects Version/s: 3.1.6
> Can't tell CXF to use a custom certstore for SSL certificate check
> --
>
> Key: CXF-8013
> URL: https://issues.apache.org/jira/browse/CXF-8013
> Project: CXF
> Issue Type: Bug
>Affects Versions: 3.1.6
>Reporter: Michel SAUMON
>Priority: Major
>
> In my cxf.xml, I declared a custom certstore because the server's certificate
> is not considered valid by the JDK:
> {code:java}
> http://www.springframework.org/schema/beans;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xmlns:sec="http://cxf.apache.org/configuration/security;
> xmlns:http="http://cxf.apache.org/transports/http/configuration;
> xmlns:jaxws="http://java.sun.com/xml/ns/jaxws;
> xsi:schemaLocation="
> http://cxf.apache.org/configuration/security
> http://cxf.apache.org/schemas/configuration/security.xsd
> http://cxf.apache.org/transports/http/configuration
> http://cxf.apache.org/schemas/configuration/http-conf.xsd
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.0.xsd;>
>
> http://myservice.xx/comweb/}ComWebSoap.http-conduit;>
>
>
>
>
>
>
>
>
>
>
> {code}
> But CXF does not take this config.
> I have still the error telling the cert is not valid :
> {code:java}
> javax.xml.ws.WebServiceException:
> org.apache.cxf.service.factory.ServiceConstructionException: Failed to create
> service.
> at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:163)
> at org.apache.cxf.jaxws.ServiceImpl.(ServiceImpl.java:129)
> at
> org.apache.cxf.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:82)
> at javax.xml.ws.Service.(Service.java:77)
> at com.sylob.cochise.myreport.ComWeb.(ComWeb.java:40)
> at
> com.sylob.cochise.myreport.ComWebTest.getComWebSoap(ComWebTest.java:101)
> at
> com.sylob.cochise.myreport.ComWebTest.testGetReporting(ComWebTest.java:136)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)
> Caused by: org.apache.cxf.service.factory.ServiceConstructionException:
> Failed to create service.
> at
> org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:87)
> at org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:218)
> at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:161)
> ... 25 more
> Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR:
> Problem parsing 'https://ctrl-talend-s95/COM_WEB/ComWeb.asmx?wsdl'.:
> javax.net.ssl.SSLHandshakeException:
> sun.security.validator.ValidatorException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target
> at com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(WSDLReaderImpl.java:2198)
> at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2390)
> at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2422)
> at
> org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:238)
> at
>
[jira] [Created] (CXF-8013) Can't tell CXF to use a custom certstore for SSL certificate check
Michel SAUMON created CXF-8013:
--
Summary: Can't tell CXF to use a custom certstore for SSL
certificate check
Key: CXF-8013
URL: https://issues.apache.org/jira/browse/CXF-8013
Project: CXF
Issue Type: Bug
Reporter: Michel SAUMON
In my cxf.xml, I declared a custom certstore because the server's certificate
is not considered valid by the JDK:
{code:java}
http://www.springframework.org/schema/beans;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xmlns:sec="http://cxf.apache.org/configuration/security;
xmlns:http="http://cxf.apache.org/transports/http/configuration;
xmlns:jaxws="http://java.sun.com/xml/ns/jaxws;
xsi:schemaLocation="
http://cxf.apache.org/configuration/security
http://cxf.apache.org/schemas/configuration/security.xsd
http://cxf.apache.org/transports/http/configuration
http://cxf.apache.org/schemas/configuration/http-conf.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd;>
http://myservice.xx/comweb/}ComWebSoap.http-conduit;>
{code}
But CXF does not take this config.
I have still the error telling the cert is not valid :
{code:java}
javax.xml.ws.WebServiceException:
org.apache.cxf.service.factory.ServiceConstructionException: Failed to create
service.
at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:163)
at org.apache.cxf.jaxws.ServiceImpl.(ServiceImpl.java:129)
at
org.apache.cxf.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:82)
at javax.xml.ws.Service.(Service.java:77)
at com.sylob.cochise.myreport.ComWeb.(ComWeb.java:40)
at com.sylob.cochise.myreport.ComWebTest.getComWebSoap(ComWebTest.java:101)
at
com.sylob.cochise.myreport.ComWebTest.testGetReporting(ComWebTest.java:136)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:252)
at junit.framework.TestSuite.run(TestSuite.java:247)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)
Caused by: org.apache.cxf.service.factory.ServiceConstructionException: Failed
to create service.
at
org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:87)
at org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:218)
at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:161)
... 25 more
Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR:
Problem parsing 'https://ctrl-talend-s95/COM_WEB/ComWeb.asmx?wsdl'.:
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException:
PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
at com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(WSDLReaderImpl.java:2198)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2390)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2422)
at
org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:238)
at
org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:163)
at
org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:85)
... 27 more
Caused by: javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at
