Return-Path: Delivered-To: apmail-cxf-users-archive@www.apache.org Received: (qmail 49290 invoked from network); 30 Sep 2008 21:18:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Sep 2008 21:18:30 -0000 Received: (qmail 41110 invoked by uid 500); 30 Sep 2008 21:18:27 -0000 Delivered-To: apmail-cxf-users-archive@cxf.apache.org Received: (qmail 41072 invoked by uid 500); 30 Sep 2008 21:18:26 -0000 Mailing-List: contact users-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@cxf.apache.org Delivered-To: mailing list users@cxf.apache.org Received: (qmail 41061 invoked by uid 99); 30 Sep 2008 21:18:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Sep 2008 14:18:26 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [64.79.199.57] (HELO server.dankulp.com) (64.79.199.57) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Sep 2008 21:17:23 +0000 Received: by server.dankulp.com (Postfix, from userid 5000) id 4DC98197CB22; Tue, 30 Sep 2008 17:17:56 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.2.5-gr0 (2008-06-10) on server.dankulp.com X-Spam-Level: X-Msg-File: /tmp/mailfilter.He2wwrqL1y Received: from [172.20.103.60] (unknown [198.112.75.205]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by server.dankulp.com (Postfix) with ESMTP id DA22D197C0BE; Tue, 30 Sep 2008 17:17:54 -0400 (EDT) From: Daniel Kulp To: users@cxf.apache.org Subject: Re: Trying to make an interceptor for WSDL Date: Tue, 30 Sep 2008 17:17:53 -0400 User-Agent: KMail/1.9.7 Cc: "Idar Borlaug" References: <469f0a1b0809260531j3dadf2efv580f43f19bbe0c3b@mail.gmail.com> <200809291024.19388.dkulp@apache.org> <469f0a1b0809300130y3312d717tcbd591c58b353d13@mail.gmail.com> In-Reply-To: <469f0a1b0809300130y3312d717tcbd591c58b353d13@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200809301717.53927.dkulp@apache.org> X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No, score=-2.5 required=3.0 tests=BAYES_00,RDNS_NONE autolearn=no version=3.2.5-gr0 On Tuesday 30 September 2008, Idar Borlaug wrote: > 2008/9/29 Daniel Kulp : > > 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? Yep. The jaxws:endpoint things in the spring config have a special property that can be set to control the published location. publishedEndpointUrl="http://......." That MAY require 2.0.7 or newer though. I'm not sure if that made it into 2.0.6. Dan > > > 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 : > >> >> > 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 > >> > dkulp@apache.org > >> > http://www.dankulp.com/blog > > > > -- > > Daniel Kulp > > dkulp@apache.org > > http://www.dankulp.com/blog -- J. Daniel Kulp Principal Engineer, IONA dkulp@apache.org http://www.dankulp.com/blog