You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by Lionel Cons <li...@cern.ch> on 2011/06/29 14:18:55 UTC

Apollo selector vs. STOMP header fields

Hiram,

I've tested the message selectors in Apollo and they seem to work fine for
some header fields. However, they seem to fail with fields containing a
dash. What I see is identical to what is seen in ActiveMQ, see
https://issues.apache.org/jira/browse/AMQ-3355.

Are header fields containing a dash supposed to work with Apollo's
selectors?

FWIW, some interesting STOMP fields do contain a dash, for instance
content-length or content-type...

Cheers,

Lionel

Re: Apollo selector vs. STOMP header fields

Posted by Hiram Chirino <hi...@hiramchirino.com>.
Yeah.. we started off with the same selector parser so we will end up
with the same issues.  I've opened up:
https://issues.apache.org/jira/browse/APLO-59

Regards,
Hiram

FuseSource
Web: http://fusesource.com/




On Wed, Jun 29, 2011 at 8:18 AM, Lionel Cons <li...@cern.ch> wrote:
> Hiram,
>
> I've tested the message selectors in Apollo and they seem to work fine for
> some header fields. However, they seem to fail with fields containing a
> dash. What I see is identical to what is seen in ActiveMQ, see
> https://issues.apache.org/jira/browse/AMQ-3355.
>
> Are header fields containing a dash supposed to work with Apollo's
> selectors?
>
> FWIW, some interesting STOMP fields do contain a dash, for instance
> content-length or content-type...
>
> Cheers,
>
> Lionel
>