Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
See why IDC MarketScape names Qlik a 2025 Leader! Read more
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Calling a https REST service with Talend Open Studio

Hi,
I just would like to call an existing RESTful webservice using tRESTRequest and tRESTResponse...
(with a HTTPS endpoint with the calling POST method and Basic Authentication) but when I execute it in Talend Open Studio, I have the error below.
Could you tell me how I can correct it please ?

org.apache.cxf.service.factory.ServiceConstructionException
at org.apache.cxf.jaxrs.JAXRSServerFactoryBean.create(JAXRSServerFactoryBean.java:209)
at test1.wssepasearch_0_1.WSSepaSearch$Thread4RestServiceProviderEndpoint.run(WSSepaSearch.java:630)
Caused by: java.lang.RuntimeException: Protocol mismatch for port -1: engine's protocol is http, the url protocol is https
at org.apache.cxf.transport.http_jetty.JettyHTTPDestination.finalizeConfig(JettyHTTPDestination.java:162)
at org.apache.cxf.transport.http.HTTPTransportFactory.getDestination(HTTPTransportFactory.java:308)
at org.apache.cxf.endpoint.ServerImpl.initDestination(ServerImpl.java:93)
at org.apache.cxf.endpoint.ServerImpl.<init>(ServerImpl.java:72)
at org.apache.cxf.jaxrs.JAXRSServerFactoryBean.create(JAXRSServerFactoryBean.java:159)
... 1 more
Caused by: java.io.IOException: Protocol mismatch for port -1: engine's protocol is http, the url protocol is https
at org.apache.cxf.transport.http_jetty.JettyHTTPServerEngineFactory.createJettyHTTPServerEngine(JettyHTTPServerEngineFactory.java:271)
at org.apache.cxf.transport.http_jetty.JettyHTTPDestination.retrieveEngine(JettyHTTPDestination.java:127)
at org.apache.cxf.transport.http_jetty.JettyHTTPDestination.finalizeConfig(JettyHTTPDestination.java:160)
... 5 more

Regards
Cédric JOUBERT
Labels (4)
11 Replies
Anonymous
Not applicable
Author

Np, thanks for spotting the problem. I've been running few demos with tRESTClient calling out to HTTPS targets but they were 'plain' HTTPS ones; hope we can fix it fast enough,
Cheers, Sergey
Anonymous
Not applicable
Author

oh ok... :-)
I'm trying to deal with the tFileFetch component... apparently, some users tested this solution with success...
I would be interested form me to find some examples of such a solution (before the RESTClient fix coming).