Re: Registering two ports on (almost) the same URL -- same path, different protocol

> On Dec 16, 2014, at 9:36 AM, Marco Rietveld wrote: > > Hi all, > > Is it possible to register a non-SSL ("normal") and SSL-configured port on > the same URL with different protocols? For example: > > http://localhost:8080/ws/Pingservice > https://localhost:8080/ws/Pingservice Not on the sa

Re: WS-Addressing : [MAPCodec] Failed to correlate message

> On Dec 16, 2014, at 8:18 AM, Manu wrote: > > If I create a unique and dynamic replyTo URL, will the destination registry > be storing each URL ? Yes. But only as long as there is a client that is using it. When the client is finalized or you call close on it, the endpoint would get cleaned

cxf 2.6 weblogic 10.3.6 java.lang.AssertionError: UNIMPLEMENTED weblogic.xml.domimpl.ElementBase.setIdAttributeNode(ElementBase.java:333)

my webservice built on cxf 2.6 java 1.7, deployed on weblogic 10.3.6 is giving this error There is similar error post with no reply ( http://cxf.547215.n5.nabble.com/Running-CXF-WSS4J-on-Weblogic-td5626091.html )

Re: cxf git commit: [CXF-6157] Support storing of OAuth2 redirection state in a session token

Hi Thorsten, All, I've updated OAuth2 SessionAuthenticityTokenProvider interface on the trunk. The reason for that is that at the moment the only way for Redirection-based services to return the redirection state as part of the authorization decision is to use form hidden fields. That would i

Re: WebClient fire & forget

Setting an exchange property is a great idea.. I will try that :-) Many thanks Sent from a mobile device > On 16 Dec 2014, at 12:01, Sergey Beryozkin wrote: > > Hi Mandy >> On 16/12/14 11:30, Mandy Warren wrote: >> This worked fine, many thanks. Just a query about the option to use the same

Two-way (mutual) SSL authentication with the Apache CXF client plugin for grails

Has anyone been able to make the Apache CXF client grails plugin work with 2-way SSL authentication? I have not been able to make it work. I posted to stackoverflow, but did not get many replies. Details are here: http://stackoverflow.com/questions/27388864/two-way-mutual-ssl-authentication-wit

Re: Rest client returning ClientException, cause: #3732

I did realize it was fictitious :-). I could only think of the actual parentheses "()" affecting it. Please provide a test case or simply download the CXF source code and debug the invocation... Sergey On 16/12/14 15:12, Kevin Schnake wrote: Sergey, My model didn't get posted intact. It is be

RE: Rest client returning ClientException, cause: #3732

Sergey, My model didn't get posted intact. It is below. methodName is fictitious. Is there more info on error: 3732? Thx! -Original Message- From: Sergey Beryozkin [mailto:sberyoz...@gmail.com] Sent: Monday, Decemb

Registering two ports on (almost) the same URL -- same path, different protocol

Hi all, Is it possible to register a non-SSL ("normal") and SSL-configured port on the same URL with different protocols? For example: http://localhost:8080/ws/Pingservice https://localhost:8080/ws/Pingservice (Note the s in the https in the second URL). I've set up a test project to try to f

Re: XML binding with JaxWsDynamicClient

Thanks Dan, that works fine. Do you known why the endpoint auto selection is not available for non-soap endpoints ? Regards, Christophe -- View this message in context: http://cxf.547215.n5.nabble.com/XML-binding-with-JaxWsDynamicClient-tp5752191p5752402.html Sent from the cxf-user mailing li

Re: WS-Addressing : [MAPCodec] Failed to correlate message

Hi again, If I create a unique and dynamic replyTo URL, will the destination registry be storing each URL ? Could this lead to an OutOfMemoryError ? Le Tue Dec 16 2014 at 13:29:56, Manu a écrit : > In org.apache.cxf.ws.addressing.impl.MAPAggregatorImpl.getDestination(Bus, > String, Message), t

Re: Async client Http transport and keep-alive timeouts

Hi Mandy I'd like to ask Dan, Aki or Oleg to comment - hopefully one of HTTP Client experts would read it :-) by the way, what about HTTPUrlConnection - does it work less efficiently ? Thanks, Sergey On 12/12/14 14:23, Mandy Warren wrote: Hi, We are using cxf version 2.7.12 and are using As

Re: WS-Addressing : [MAPCodec] Failed to correlate message

In org.apache.cxf.ws.addressing.impl.MAPAggregatorImpl.getDestination(Bus, String, Message), the interceptor register a MessageObserver on the destination. So the second web service call will replace the first MessageObserver. This way the interceptor chain registered (and the MAPCodec) will not be

Re: WebClient fire & forget

Hi Mandy On 16/12/14 11:30, Mandy Warren wrote: This worked fine, many thanks. Just a query about the option to use the same thread instead of spawning a new one... Does that mean service 1 waits til service 2 completes execution or does it return at an earlier phase? I ask because currently

Re: WS-Addressing : [MAPCodec] Failed to correlate message

It seems worse than I first thought ... If 2 requests for the same asynchronous web service run in parallel, the same problem occurs. Can someone help me please ? I'm totally lost ... Le Mon Dec 15 2014 at 16:59:14, Manu a écrit : It seems that when there is multiple asynchronous web service usi

Re: WebClient fire & forget

This worked fine, many thanks. Just a query about the option to use the same thread instead of spawning a new one... Does that mean service 1 waits til service 2 completes execution or does it return at an earlier phase? I ask because currently our pattern is to place data about the call into a