onent-and-the-startDelayedSeconds-attribute-tp5718764p5718987.html
Sent from the Camel Development mailing list archive at Nabble.com.
Thanks for the hint, but unfortunately we stick to 2.6.0 with this service
in the time being.
Best,
Christian
On Fri, Sep 7, 2012 at 1:28 PM, Claus Ibsen wrote:
> Hi
>
> If you use a recent version of Camel then in the unit test you can
> override the isUseAdviceWith method and return true.
>
Hi
If you use a recent version of Camel then in the unit test you can
override the isUseAdviceWith method and return true.
So bottom of:
http://camel.apache.org/advicewith.html
Then it ought to defer starting Camel, and you can do your
interceptors and whatnot. And then start Camel.
On Fri, Se
Thanks for the detailed explanation Claus. I create a JIRA for it [1] and
will go ahead.
Some details about our "problem":
We face this only in our unit tests where we use "interseptSendToEndpoint"
to mock an endpoint and throw an exception to test the exceptional use
case. Because the Quartz comp
On Fri, Sep 7, 2012 at 12:44 PM, Christian Müller
wrote:
> Is there any reason why we don't support 'startDelayedSeconds' as URL
> option? At present, we only supporting this by directly setting this in the
> component:
>
> value="com/mycompany/myquartz.properties"/>
>
>
> If not, I will go
Sorry, I mean:
Best,
Christian
On Fri, Sep 7, 2012 at 12:44 PM, Christian Müller <
christian.muel...@gmail.com> wrote:
> Is there any reason why we don't support 'startDelayedSeconds' as URL
> option? At present, we only supporting this by directly setting this in the
> component:
> clas
Is there any reason why we don't support 'startDelayedSeconds' as URL
option? At present, we only supporting this by directly setting this in the
component:
If not, I will go ahead and fix it, so that we can use it as URL option like
quartz://myGroup/myTimerName?startDelayedSeconds=5
Best,
