Wow. Interesting case. You're going to have to write a custom transport for this. Normally, a custom transport isn't that hard. A Conduit for the client side and a Destination for the server side. However, in this case where the conduit becomes a destination and vice-versa might require a bit extra work under the covers to achieve.
Dan On Fri December 4 2009 4:16:29 am Fromm, Stefan wrote: > Hello, > > I have the following scenario. A web service is running on the internet. > My intranet server connects to this web service. After connection the > web service is supposed to reuse the connection, become the client and > send requests to the intranet server. This is firewall-friendly, because > I do not have to open my intranet firewall to allow incoming requests. > Instead I have to open the firewall for outgoing requests only. Once the > connection is established, the web service could reuse it and send its > requests. Using plain sockets it is simple to implement such a scenario. > My question is, if this would also be possible with CXF? The underlying > protocol can be HTTP(S) or TCP(S). I would need some hints where to > start from reading documentation, because I am new to CXF. > > Best regards > Stefan Fromm > -- Daniel Kulp [email protected] http://www.dankulp.com/blog
