Mailing-List: contact users-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cxf.apache.org
Received-SPF: pass (athena.apache.org: domain of manoelkazza@gmail.com
 designates 209.85.213.169 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=WTJrPfxG27o7D2dcG3ZLTENpyL9dr2uYFN30+ItFXVnKBhCsDzEBVZYxtgNBOBDaRp
         rjaidSfnmqIyoxRyjiJM5VZrQgKcJhDf9eaikSF3zfO1qJoP6Ck+btA4q5v0szUIsEsA
         Iv2SxOTOqcn120a9tzKLBbpgcG95Q5EsvgEAU=
MIME-Version: 1.0
In-Reply-To: <AANLkTimUt+HxVXSm8=7uBKoDt8_A6Vekdi9uDFyS+pnf@mail.gmail.com>
References: <AANLkTin8YxmUSNj4MQa_ES=aMXw+efuSpit22MAc9k43@mail.gmail.com>
	<201011301601.29528.dkulp@apache.org>
	<AANLkTikhUaQHPgRWLvb9oLK8ZyNZm6h=b05jFXAVWHqr@mail.gmail.com>
	<201012011407.11330.dkulp@apache.org>
	<AANLkTi=5+9jLnnH56=7TfQ5-wR8QgwoSh7VxWLGew-yX@mail.gmail.com>
	<AANLkTikwVNEA3s4ura275M16f=CUYJxADG=n+oeGR6TL@mail.gmail.com>
	<AANLkTi=Vk8i_ig=eGoL2mBW5g=hSOeAwkbqNu8dE3JGK@mail.gmail.com>
	<AANLkTik3RvkLWm3PRmgp9XXVGiKPGrxfHPJ+82k9Zx6Y@mail.gmail.com>
	<AANLkTimUt+HxVXSm8=7uBKoDt8_A6Vekdi9uDFyS+pnf@mail.gmail.com>
Date: Mon, 6 Dec 2010 10:16:54 +0100
Message-ID: <AANLkTika6tkgmE9NMcc-s_G3u_osndz2YpBGsvhgxcY9@mail.gmail.com>
Subject: Re: Interceptors: How to handle an unknown request?
From: Manoel Farrugia <manoelkazza@gmail.com>
To: users@cxf.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Sorry but I am new with CXF and have not understand the last post Sergey


On Thu, Dec 2, 2010 at 11:52 AM, Sergey Beryozkin <sberyozkin@gmail.com> wr=
ote:
> Having a custom CXF invoker is probably one option, it should be able to
> ensure the right Method is invoked,
> another option is to register a custom CXF ServletFilter which would prov=
ide
> a custom HttpServletRequest which would in turn manipulate the request bo=
dy
> such that CXF is made to believe it is getGreeting() which has to be
> invoked.
> You may also want to debug and check how CXF SOAP interceptors determine =
the
> method name and may be you can register a custom XMLStreamReader which wi=
ll
> make CXF to invoke getGreeting.
>
> Sergey
>
>
> On Thu, Dec 2, 2010 at 10:37 AM, Manoel Farrugia <manoelkazza@gmail.com>w=
rote:
>
>> No I have only getGreeting implemented and want that every other wrong
>> request is directed to getGreeting.
>>
>> If one requests getGreeting2 it directs him to getGreeting.
>>
>>
>> On Thu, Dec 2, 2010 at 11:34 AM, Sergey Beryozkin <sberyozkin@gmail.com>
>> wrote:
>> > Do you actually have getGreeting2 implemented ? Example, do you have t=
wo
>> > SOAP endpoints, one implementing getGreeting and one getGreeting2 and =
you
>> > want the consumers of getGreeting2 be able to work with the old
>> > getGreeting() ?
>> >
>> > cheers, Sergey
>> >
>> > On Thu, Dec 2, 2010 at 9:43 AM, Manoel Farrugia <manoelkazza@gmail.com
>> >wrote:
>> >
>> >> I can even scrap the idea of Interceptors if there is a better way to
>> >> do my wanted job!
>> >>
>> >> Instead of receiving soap:ServerNo such operation: getGreeting2 (HTTP
>> >> GET PATH_INFO: /HelloWorldWebServices/HelloWorldPort/getGreeting2) I
>> >> want to see the getGreeting response!
>> >>
>> >> How can I do it in CXF Web Services?
>> >>
>> >>
>> >>
>> >> On Wed, Dec 1, 2010 at 8:10 PM, Manoel Farrugia <manoelkazza@gmail.co=
m>
>> >> wrote:
>> >> > I am not restricted to handleFault only. I want to redirect any wro=
ng
>> >> > methods to getGreeting() method.
>> >> >
>> >> > On Wed, Dec 1, 2010 at 8:07 PM, Daniel Kulp <dkulp@apache.org> wrot=
e:
>> >> >>
>> >> >> On Wednesday 01 December 2010 5:49:41 am Manoel Farrugia wrote:
>> >> >> > Something like this:
>> >> >> >
>> >> >> > public void handleFault(Message message) {
>> >> >> > =A0 =A0 =A0System.out.println("------FAAAAAUUUUUUUULLLLLLTTTTTT-=
------");
>> >> >> >
>> >> >> > =A0 =A0 =A0String path =3D (String)message.get(Message.PATH_INFO=
);
>> >> >> > =A0 =A0 =A0String basePath =3D (String)message.get(Message.BASE_=
PATH);
>> >> >> > =A0 =A0 =A0String query =3D (String)message.get(Message.QUERY_ST=
RING);
>> >> >> > =A0 =A0 =A0System.out.println("Path: "+path+". BasePath: "+baseP=
ath+".
>> >> Query:
>> >> >> > "+query+".");
>> >> >> > =A0 =A0 =A0System.out.println("------FAAAAAUUUUUUUULLLLLLTTTTTT-=
------");
>> >> >> >
>> >> >> > =A0 =A0 =A0message.put(Message.PATH_INFO,
>> >> >> > "/HelloWorldWebServices/HelloWorldPort/getGreeting");
>> >> >> >
>> >> >> > =A0 =A0 =A0path =3D (String)message.get(Message.PATH_INFO);
>> >> >> > =A0 =A0 =A0System.out.println("NEW PATH: "+path);
>> >> >> > =A0 =A0 }
>> >> >> >
>> >> >> > That is changing the message's pathinfo from the wrong one
>> >> >> > to /HelloWorldWebServices/HelloWorldPort/getGreeting
>> >> >> >
>> >> >> > But I want to direct to
>> >> >> > /HelloWorldWebServices/HelloWorldPort/getGreeting
>> >> >> > from the handleFault method.
>> >> >> > How should I do this?
>> >> >>
>> >> >> From handleFault? =A0 Hmm... =A0No idea really.
>> >> >>
>> >> >> You =A0could TRY to do something like
>> >> >> message.getInterceptorChain().reset();
>> >> >> message.getIntercetporChain().processMessage(message);
>> >> >> message.getInterceptorChain().pause();
>> >> >>
>> >> >> or similar. =A0I really have no idea what that would do. =A0 Hones=
tly,
>> once
>> >> >> the
>> >> >> fault occurs, things are somewhat left in an unpredictable state a=
nd
>> I'm
>> >> >> not
>> >> >> sure what would happen.
>> >> >>
>> >> >> Dan
>> >> >>
>> >> >>
>> >> >>
>> >> >> >
>> >> >> > On Tue, Nov 30, 2010 at 10:01 PM, Daniel Kulp <dkulp@apache.org>
>> >> wrote:
>> >> >> > > On Tuesday 30 November 2010 5:31:10 am Manoel Farrugia wrote:
>> >> >> > > > As a web service I have a getGreeting() method which is
>> accessed
>> >> by:
>> >> >> > >
>> >> >> > >
>> >>
>> http://localhost:8080/HelloWorldWebServices/services/HelloWorldPort/getG=
r
>> >> >> > > ee
>> >> >> > >
>> >> >> > > > ting<
>> >> >> > >
>> >> >> > >
>> >> http://localhost:8080/HelloWorldWebServices/services/HelloWorldPort/g=
e
>> >> >> > >
>> >> >> > > > tGreeting1?arg0=3DManoel>
>> >> >> > > >
>> >> >> > > > Now I want that any other request method which does not exis=
t
>> in
>> >> my
>> >> >> > > > web
>> >> >> > > > service (for example getGreetingMe()) is redirected to
>> >> getGreeting()
>> >> >> > > > as
>> >> >> > >
>> >> >> > > the
>> >> >> > >
>> >> >> > > > address above.
>> >> >> > > >
>> >> >> > > > How should I tackle this idea?
>> >> >> > >
>> >> >> > > If =A0this is just for the "GET" requests, it shouldn't be too
>> hard.
>> >> >> > >
>> >> >> > > String path =3D (String)message.get(Message.PATH_INFO);
>> >> >> > > String basePath =3D (String)message.get(Message.BASE_PATH);
>> >> >> > > String query =3D (String)message.get(Message.QUERY_STRING);
>> >> >> > >
>> >> >> > > would get you the values that were sent in. =A0You would just =
need
>> to
>> >> >> > > reset
>> >> >> > > them
>> >> >> > > to the "getGreeting" versions of those via message.put(...) ty=
pe
>> >> >> > > things.
>> >> >> > >
>> >> >> > > --
>> >> >> > > Daniel Kulp
>> >> >> > > dkulp@apache.org
>> >> >> > > http://dankulp.com/blog
>> >> >>
>> >> >> --
>> >> >> Daniel Kulp
>> >> >> dkulp@apache.org
>> >> >> http://dankulp.com/blog
>> >> >
>> >> >
>> >>
>> >
>>
>