Re: Apache CXF won't load ReceiveTimeout from conduit file

2017-02-21 Thread martin.pelikan
Hi, I have opened a new bug in CXF Jira https://issues.apache.org/jira/browse/CXF-7260. You can watch the progress there. Martin -- View this message in context: http://camel.465427.n5.nabble.com/Camel-CXF-won-t-load-ReceiveTimeout-from-conduit-file-tp5794169p5794177.html Sent from the Camel

Re: Apache CXF won't load ReceiveTimeout from conduit file

2017-02-21 Thread martin.pelikan
Hi Claus, I thought the issue concerns the Apache Camel CXF components as Blueprint leverages http://camel.apache.org/schema/blueprint/cxf and http://camel.apache.org/schema/blueprint. Error I am getting is from DelayService (Blueprint Proxy implementing Camel CXF). Could you elaborate more why

Apache CXF won't load ReceiveTimeout from conduit file

2017-02-21 Thread martin.pelikan
Hello, configuration ReceiveTimeout does not work via conduit file. Scenario: Published SOAP service DelayService with SSL on port 8443. This service calls another service SOAP Web service, where thread.sleep(70s) is implemented. DelayService is invoked via SOAPUI. Expected result: Successful re

Re: WS-SecurityPolicy and WS-Timestamp

2016-11-25 Thread martin.pelikan
Hi Claus, I solved the problem. First approach was to leverage wss4jOutInterceptor. I was able to generate WS-UsernameToken, WS-Timestamp and WS-Addressing in request, but unfortunatelly in wrong order (Timestamp->UsernameToken->Addressing). I wasn't able to change the element order, thus had to f

WS-SecurityPolicy and WS-Timestamp

2016-11-22 Thread martin.pelikan
Hi, I have a simple SOAP Proxy (input is non-secured, backend is secured by UsernameToken) in Spring, using Camel CXF and I would like to implement WS-Timestamp on producer endpoint. We are using WS-SecurityPolicy to authenticate against backend. As I understand there is one option - to leverage w

Re: Camel CXF - wrong Content-Type sent

2016-11-22 Thread martin.pelikan
Manually editing WSDL and changing to (and all other elements with prefix 'soap') did the trick. Thanks for pushing me, Aki. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-CXF-wrong-Content-Type-sent-tp5790368p5790371.html Sent from the Camel - Users mailing list arc

Re: Camel CXF - wrong Content-Type sent

2016-11-22 Thread martin.pelikan
Hi Aki, I specified my question. You are correct about using WSDL v1.1. But set binding to SOAP1.2 did not help http://cxf.apache.org/blueprint/bindings/soap"; /> Here is stack trace from Karaf: RouteId ProcessorId

Camel CXF - wrong Content-Type sent

2016-11-22 Thread martin.pelikan
Hi all, I am trying to send SOAP request with Content-Type application/soap+xml. I call SOAPConsumer with correct header, in the middle of the route header is modified once again (to be sure), but in the end I get HTTP response '415: Cannot process the message because the content type 'text/xml; c

Jetty overrides multiple securityHandles

2016-06-10 Thread martin.pelikan
Hello, I am trying to solve a problem with using multiple securityHandlers across multiple Proxies (XML files) running on the same port in karaf. Let's say proxies are configures like this, differs only in the id of the securityHandler and the role. Everything else is same for every XML file. Al