Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.216.45 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=hJuCS8yAi8CJaTwr1xpTrPzOJNSlJw3cSaau1zp1hBAnUp2k2eceA/eOJZONIUARCe
         2EX7qxljTyF/5b7XWfpEilhVS0Qbsy5Dxb4RcPU7ShTguNf3rEAGLaHIGKrWK2VuoVyH
         Y0YICLZ6DKLQobps8wqj9FoarRGJCCdCWBWZA=
MIME-Version: 1.0
In-Reply-To: <1294846065198-3338324.post@n5.nabble.com>
References: <1294798833563-3337627.post@n5.nabble.com>
 <AANLkTikXTQ2ouPxV6Bikj-dNkLhNgxOj=RX_0CZoH0n2@mail.gmail.com>
 <1294846065198-3338324.post@n5.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Sun, 16 Jan 2011 11:26:03 +0100
Message-ID: <AANLkTi=3LBcG0vVxw0jAY_=vuq_kjWQfqXsu2UX8wE_Q@mail.gmail.com>
Subject: Re: ActiveMQ ?query='..' URI parameter not accepted
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Jan 12, 2011 at 4:27 PM, Barry Kaplan <groups1@memelet.com> wrote:
>
> from("jms:topic:mytopic?query='from=today'") .process { ... }
>
> Its really that simple, although the value for query can be any string.
>
> For that topic I have defined a custom QueryBasedSubscriptionRecoveryPolicy
> to which activemq will provide the query parameter value when a client
> subscribes, giving my policy impl the chance to send the historical messages
> to the particular subscriber.
>
> But I'm guessing Claus that you already know all this about activemq, so am
> I misunderstanding what kind of example you are asking for?
>

How do you perceive that the JmsComponent / ActiveMQ component should
figure out the query parameter is for a custom
QueryBasedSubscriptionRecoveryPolicy ?

There are a zillion options in ActiveMQ and not all is possible to
compute from an uri string where they actually should be used.

I think to remedy they there need to be more prefixes, so query would
have to be prefixed with something that ties it to recoveryPolicy, so
maybe? ?recovery.policy.queue=XXXX


> However, there are also other uri paramters that activemq will process that
> the jms/activemq components won't let thru. It seems that that the camel
> components pretty much must duplicate the activemq uri model release per
> release. Since activemq will validate the uri, it seems that the activemq
> component (not the jms component though) should not fail for parameters it
> does not recognize. If this were the case though, I'm guessing that some
> errors from activemq might come much later than they would if issue by the
> camel component. But surely this can be configurable decision.
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/ActiveMQ-query-URI-parameter-not-accepted-tp3337627p3338324.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>


-- 
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/