Agreed, this would be very handly to be able to easily defines filter
in the xml, instead of having to hand write them in the listener.
On 9/28/07, Przemyslaw Budzik <[EMAIL PROTECTED]> wrote:
>
>
> gnodet wrote:
> >
> > We need to have better support for endpoint filtering, but once we
> > have this, it should be quite easy to add your interceptors and easily
> > control the exchanges you receive.
> > And this would just use wrap the provided ExchangeListener with a
> > wrapping implementation using the define filtering. Makes sense ?
> >
>
> Even regarding 3.2 funcitonality and listeners based approach it would be
> possibly nice
> to have listener method enhanced by additional parameter - sort of filter
> like function.
> I mean something that provides "accept" method. For now all that
> functionality I have made by myself (filtering based on checking QName
> against
> startsWith("http://.../servicename";)).
>
> --
> View this message in context:
> http://www.nabble.com/Interceptors-like-functionality-tf4515215s12049.html#a12937836
> Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
