Question on Adding Link to the CXF Resources and Articles Page

Good Day, My name is Michael Hoffman and I am reaching out with a question related to adding a link to the CXF resources and articles page. I have worked with CXF for the past year and a half and recently contributed an on-line training course around it for Pluralsight.com. The reason I ch

Re: Http proxy with STS

I see timeout too but only for the second request. First request doesn't use proxy: 28.04.2014 16:37:01 org.apache.cxf.services.SecurityTokenService.SecurityTokenService.SecurityTokenService INFO: Outbound Message --- ID: 1 Address: https://URL./account/ Encoding:

Re: Http proxy with STS

Could you share how you are configuring the client using spring? I tested using CXF 3.0.0-SNAPSHOT and a http Conduit with a ReceiveTimeout value set, and it appears to be picking it up. Colm. On Mon, Apr 28, 2014 at 5:03 PM, lotos wrote: > Unfortunately it's the same problem. Conduit from the

Re: SOAP over WebSocket

Hi Przemyslaw, the http connections need no necessarily get closed after each call, so I don't think this is a problem. But hosting an HTTP endpoint at the client is often not possible by its own limitation or blocked by the network infrastructure. Another disadvantage of the conventional decoupled

Re: SOAP over WebSocket

I hope this small diagram is self-explanatory http://postimg.org/image/blg7dk2o7/ On Tue, Apr 29, 2014 at 3:20 PM, Przemyslaw Bielicki wrote: > Yes, this is what would be nice to have as a solution with two HTTP > connections is really bad. Not only your client needs to understand HTTP > (acts a

Re: SOAP over WebSocket

Hi Przemyslaw, Andrei's blog (the one linked in his earlier reply http://ashakirin-cxf-async.blogspot.de/) has some examples about asynchronous soap calls over HTTP. But the limitation of this approach is that you will need two separate HTTP connections: one from the client to the service and the o

Re: SOAP over WebSocket

Yes, this is what would be nice to have as a solution with two HTTP connections is really bad. Not only your client needs to understand HTTP (acts as a server), but also a HTTP connection is closed after 202 response! This is huge waste of resources, especially if you have use cases with 1000 - 300

Re: Http proxy with STS

Yep. Could you create a JIRA and I'll take a look? Colm. On Mon, Apr 28, 2014 at 5:03 PM, lotos wrote: > Unfortunately it's the same problem. Conduit from the configuration isn't > used by STS. Looks like a bug. > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Http-

Re: SOAP over WebSocket

https://github.com/pbielicki/soap-websocket-cxf I tested soap-websocket-webapp in both Wildfly 8.0.1-SNAPSHOT and Tomcat 8.0.3 (for Tomcat you need to add extra dependency of commons-logging). You need to start ActiveMQ on the same machine on default port 61616. You can use soap-websocket-client

Re: SOAP over WebSocket

https://github.com/pbielicki/soap-websocket-cxf I tested soap-websocket-webapp in both Wildfly 8.0.1-SNAPSHOT and Tomcat 8.0.3 (for Tomcat you need to add extra dependency of commons-logging). You need to start ActiveMQ on the same machine on default port 61616. You can use soap-websocket-client

Re: SOAP over WebSocket

Hi Aki, Btw. what do you call asynchronous SOAP over HTTP? How do you get a response when it's ready? For me, HTTP is out of question as it's synchronous protocol, whatever tricks you make after :) My multiplex needs is a real bidirectional, full-duplex protocol. Cheers, Przemyslaw -- View th