sage with different properties.
> They both behave the same.
> So based on what you say, I assume that it is correct for `NOT(null)` to
> yield `false` instead of `true`.
>
> Jan
>
> -Original Message-
> From: Justin Bertram
> Sent: středa 11. září 2024 16:09
&
-Original Message-
From: Justin Bertram
Sent: středa 11. září 2024 16:09
To: users@activemq.apache.org
Subject: Re: Filtering messages with no properties/headers in Artemis
> ...my main concern has been the difference between a message that has
properties which don't match and a mess
between a message that has properties which
> don't match and a message that does not have any properties at all.
>
> Jan
>
>
>
> From: Justin Bertram
> Sent: Wednesday, September 11, 2024 3:04:42 PM
> To: users@activemq.apache.o
Sent: Wednesday, September 11, 2024 3:04:42 PM
To: users@activemq.apache.org
Subject: Re: Filtering messages with no properties/headers in Artemis
What you're seeing is, in fact, the expected behavior. As noted in the
documentation [1] the ActiveMQ Artemis filter syntax is based on the same
subset
What you're seeing is, in fact, the expected behavior. As noted in the
documentation [1] the ActiveMQ Artemis filter syntax is based on the same
subset of the SQL 92 syntax as JMS/Jakarta selectors and that documentation
[2] states:
If a property that does not exist in a message is referenced,
