Re: "selector:" header on subsequent GET requests are ignored

["Steve.V." <st...@sas.com>]

I am re-wording the previous post since it may not be clear.

Within the scope of a REST client session, the first "selector:" header I
send with a GET request is honored.  However, selector headers in subsequent
GET requests within the session are ignored in favor of the first selector
header that prompted the creation of the consumer.

I assume the first GET request causes a consumer to be created over in the
broker's JVM, the subsequent GET requests use that consumer, and any
selector headers sent with subsequent GET requests will be ignored  because
they are re-using the original consumer.

It would be nice if the broker would notice subsequent selector headers and
re-create the consumer when the selector is different from the previous GET
request within the session.  

Without that behavior, I think a client using the REST interface must
re-connect every time it wants to change a message selector.  Or, is there
another way?

Should I enter a JIRA asking for that behavior?

Bummed,
Steve V.



-----
Stephen Vincent
--
View this message in context: http://activemq.2283324.n4.nabble.com/selector-header-on-subsequent-GET-requests-are-ignored-tp4658368p4660819.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.