In the final case that you outline below, you would have to make the XSLT Router the subscriber, correct?
> -----Original Message----- > From: Guillaume Nodet [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 07, 2005 8:17 AM > To: [email protected] > Subject: Re: [servicemix-user] Publish-subscribe and filtering > > > Hi Jonathan. > > The filtering used in the ServiceMix specific pub/sub model, > is really > simple : you can provide > on the subscription spec, a bean that must implement a given > interface > that allows exchange filtering. > If the exchange does not match, it is discarded (for this > subscription). > > In WS-Notification, currently the only way is to use jms > selectors which > will be applied by the > underlying activemq broker. However this is quite useless, as people > will want to filter on the > content of the notification message. This should be done > using xpath on > the notification message, > but this has not been implemented yet. > > For the moment, the best way would be to put an xslt router (which do > handle in-only) in between > the notification broker and the subscriber so that it can filter the > messages and discard them. I agree > that this is not the best solution ... > > Cheers, > Guillaume Nodet > > [EMAIL PROTECTED] wrote: > > >I am curious to understand how subscription filtering is > implemented within > >the pub-sub model of ServiceMix. Is it implemented through > WS-Notification > >or another mechanism? Is there a good example of filtering > in the source > >code? Perhaps I am thinking about this the wrong way - any help is > >appreciated. > > > >/jonathan > > > > > > > > >
