Re: How to do a divert using an xpath filter?
thanks for that quick answer, you solved some serious headscratching.
Is this documented anywhere? I think I read all the documentation of diverts but this isn't mentioned and there also doesn't seem to be any logging/exception going on.
Would this be considered a bug or a feature request or...?
Also, do I read this correctly, in my filter expressions right now I can use all AMQ* properties as well as any other header(!) key/value pair? Everything else will be silently ignored?
Any recommendation on how we could achieve this kind of divert with filtering in Artemis?
Am Mittwoch, 17. Oktober 2018, 03:27:17 MESZ hat Justin Bertram <jbertram@xxxxxxxxxx> Folgendes geschrieben:
This isn't implemented yet. See here .
That said, it doesn't appear that it would be that hard to implement.
On Tue, Oct 16, 2018 at 6:32 PM Frank Michael <firstname.lastname@example.org>
> Hi, I'm using version 2.6.3 of Artemis and trying to set up a divert from
> one queue to another using an xpath filter. Unfortunately this doesn't work
> as my XML Test messages are not getting diverted but stay in the incoming
> My adresses in broker.xml look like this <addresses> <address
> name="DLQ"> <anycast> <queue name="DLQ" />
> </anycast> </address> <address name="ExpiryQueue">
> <anycast> <queue name="ExpiryQueue" />
> </anycast> </address>
> <address name="Incoming"> <anycast>
> <queue name="Incoming" /> </anycast> </address>
> <address name="XMLMessages">
> <anycast> <queue name="XMLMessages" />
> </anycast> </address> </addresses>
> My divert looks like this <diverts> <divert name="xmldivert">
> <filter string="XPATH
> <exclusive>true</exclusive> </divert> </diverts>
> My XML message looks like this<ContractedTimeTableMsg> <Message
> type="123"> </Message></ContractedTimeTableMsg>
> Is it possible to use an XPATH Filter like this in a divert? If not, is
> there another, correct way to do it?I'm using Java 8 and a standalone
> installation of Artemis. Xalan is on the classpath, I tried version 2.6 and
> version 2.7.If this is generally the correct way, how would you debug this?