> JAX-WS handlers are designed for cross-web stack portability, so you can > move your web service to Metro or Spring WS without coding change. Since > portability is not a concern, by virtue of the fact that it would be desired > to attach the handlers via a CXF-specific bus, the developer will usually > (always?) want to use interceptors instead > (http://www.jroller.com/gmazza/entry/jaxwshandlers_to_cxfinterceptors), as > they're normally faster.
Hmmm, I agree on that such a *configuration* would be CXF-specific. But the actual handlers would still be portable between JAX-WS implementations. So IMO allowing a CXF-specific global configuration of per se portable handlers would be beneficial for scenarios, where common handlers are configured for all endpoints. When migrating to another stack the handlers could remain unchanged, only the configuration would have to be adapted (which it has to be anyways, as e.g. Metro naturally couldn't handle CXF's Spring configuration). Performance is another story, though. Do you have any numbers how much faster interceptors are than handlers? --Gunnar 2011/6/16 Glen Mazza <[email protected]>: > On 06/16/2011 03:31 AM, Dirk Rudolph wrote: >> >> Can you explain, what is the reason for configuring handler only per >> endpoint? >> Wouldn't it be a nice feature configuring them globally if necessary? >> > > I guess it would be partly philosophical, partly due to lack of demand, > partly due to having such functionality added in being a potential source of > bugs. > > What is a JAX-WS handler, *including* how you connect it to the web service > or client, is defined in the JAX-WS specification. Arguably, if you could > connect it any other way than defined (such as with a CXF bus) it wouldn't > be a JAX-WS handler. :) > > JAX-WS handlers are designed for cross-web stack portability, so you can > move your web service to Metro or Spring WS without coding change. Since > portability is not a concern, by virtue of the fact that it would be desired > to attach the handlers via a CXF-specific bus, the developer will usually > (always?) want to use interceptors instead > (http://www.jroller.com/gmazza/entry/jaxwshandlers_to_cxfinterceptors), as > they're normally faster. > > Glen > > > > >> I also use one JAX-WS Handler in all my endpoints. >> >> Thanks, Dirk >> >> -----Ursprüngliche Nachricht----- >> Von: Willem Jiang [mailto:[email protected]] >> Gesendet: Donnerstag, 16. Juni 2011 06:13 >> An: [email protected] >> Betreff: Re: Globally specifying JAX-WS handlers >> >> No, JAX-WS handlers are configured per endpoint. >> >> On 6/16/11 4:34 AM, Gunnar Morling wrote: >>> >>> Hi, >>> >>> according to the documentation [1] one can specify interceptors on the >>> bus level, which will then be applied to all endpoints. Is the same >>> also possible for JAX-WS handlers? >>> >>> Thanks, Gunnar >>> >>> [1] http://cxf.apache.org/docs/bus-configuration.html >>> >> > > > -- > Glen Mazza > Software Engineer, Talend (http://www.talend.com) > blog: http://www.jroller.com/gmazza > > >
