2008/9/29 Daniel Kulp <[EMAIL PROTECTED]>: > On Monday 29 September 2008 3:04:59 am idar wrote: >> Hum... I am using a WSDL first approach, and the port url in the WSDL file >> is not rewritten by CXF as the urls to xsd schema are. Is a >> WSDLQueryHandler the best approach to rewrite the wsdl:port adress? > > CXF SHOULD be re-writing the addresses. If not, that's a problem.
It did fix this, i rewrote all my targetnamespace and fixed on some service names, so they corresponded to the names if i generated a wsdl. > The NORMAL cause for this is a mismatch between the servicename and > endpoint/port names in the spring config/annotations. The latest 2.1.3 > snapshots now warn about that on the console. If you could try the 2.1.3 > snapshots and see if that helps, that would be great. I am using mule 2.0.2 and it uses CXF 2.0.6 so 2.1.3 is major work for me. But i found a solution. I am also interested in being able to affect the rewriting of the urls, if i deploy my webservice to a cluster i want to be able to specify the host. Is this easily possible? > Dan > > >> >> dkulp wrote: >> > 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 > > > > -- > Daniel Kulp > [EMAIL PROTECTED] > http://www.dankulp.com/blog > -- Idar
