On Wednesday 10 November 2010 7:20:54 pm Joe Lin wrote: > Hi, > > I'm trying to implement a customize org.apache.cxf.transport.Destination by > extending AbstractDestination. In the Destination interface there is a > method called getBackChannel() and the description reads like: > > "Retreive a back-channel Conduit, which must be policy-compatible with the > current Message and associated Destination. For example compatible Quality > of Protection must be asserted on the back-channel" > > I still do not understand what is the purpose of a 'back-channel' and when > it is used to properly implement my Destination. > > A more elaborated description will be very helpful.
The very basic description of what the back channel is is that its where the reply is sent to. The equivalent of the HttpServletResponse type thing in a servlet. For MOST use cases, when the response message is created, it calls that method to setup the conduit where the response will be written. The only "funny" cases occur around the WSAddressing and WS-RM use cases that need separate side channels and such, but even with CXF 2.3.0, that has been significantly cleaned up so the destination doesn't really need to worry about it as much, if at all. -- Daniel Kulp [email protected] http://dankulp.com/blog
