Yea. Very early on, a decision was made to add special "QueryHandlers" that allow the HTTP targets to filter through things that aren't "service related" things. The WSDL returning is implemented as a query handler (WSDLQueryHandler). Thus, the interceptors don't come into play for it.
You can register your own QueryHandler which would run before ours, but you would need to do all of the wsdl stuff. (You could use our code as a base) Dan On Friday 26 September 2008 9:33:20 am Andrew Clegg wrote: > 2008/9/26 Idar Borlaug <[EMAIL PROTECTED]>: > > Hi > > > > I am trying to create an interceptor that will trigger when someone > > asks for the WSDL. I want to rewrite it based on some settings. > > I thought an interceptor would be a good way of doing this. But my > > interceptors only trigger on method calls. Even LoggingOutInterceptor > > dosen't trigger on WSDL. > > Umm, perhaps someone more knowledgeable will correct me if I'm wrong, > but I don't think interceptors are used in requests for the WSDL at > all. Because you're not invoking a web service when you request the > WSDL. > > What exactly are you trying to do -- modify the content of the WSDL on > the way out? > > Andrew. -- Daniel Kulp [EMAIL PROTECTED] http://www.dankulp.com/blog
