You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@camel.apache.org by moxford <mo...@gmail.com> on 2013/04/10 04:13:21 UTC

camel-quartz 2.10.4 against quartz 2.1.7 bug?

Exception in thread "main" java.lang.NoSuchMethodError:
org.quartz.Scheduler.getTrigger(Ljava/lang/String;Ljava/lang/String;)Lorg/quartz/Trigger;
	at
org.apache.camel.component.quartz.QuartzComponent.createEndpoint(QuartzComponent.java:134)
	at
org.apache.camel.component.quartz.QuartzComponent.createEndpoint(QuartzComponent.java:54)

Looks like the "getTrigger()" call now takes a TriggerKey instead of a pair
of string params.
I just checked the tip out of SVN and did not see a fix.

Offending line from Camel QuartzComponent.class:
trigger = getScheduler().getTrigger(*name, group*);

Scheduler.class from Quartz 2.1.7
    /**
     * Get the <code>{@link Trigger}</code> instance with the given key.
     * 
     * <p>The returned Trigger object will be a snap-shot of the actual
stored
     * trigger.  If you wish to modify the trigger, you must re-store the
     * trigger afterward (e.g. see {@link #rescheduleJob(TriggerKey,
Trigger)}).
     * </p>
     */
    Trigger getTrigger(*TriggerKey triggerKey*)
        throws SchedulerException;

Is anyone working on this?

Thanks!

-mox




--
View this message in context: http://camel.465427.n5.nabble.com/camel-quartz-2-10-4-against-quartz-2-1-7-bug-tp5730615.html
Sent from the Camel Development mailing list archive at Nabble.com.

Re: camel-quartz 2.10.4 against quartz 2.1.7 bug?

Posted by moxford <mo...@gmail.com>.

Thanks for the update.

Recommend putting this information on the documentation page to prevent
future inquiries.

http://camel.apache.org/quartz.html has no information about version
(in-)compatibility.

Thanks,

-mox



--
View this message in context: http://camel.465427.n5.nabble.com/camel-quartz-2-10-4-against-quartz-2-1-7-bug-tp5730615p5730677.html
Sent from the Camel Development mailing list archive at Nabble.com.

Re: camel-quartz 2.10.4 against quartz 2.1.7 bug?

Posted by Claus Ibsen <cl...@gmail.com>.

You need to use Quartz 1.x.
Quartz 2.x is not compatible with 1.x and not supported with camel-quartz.

On Wed, Apr 10, 2013 at 4:13 AM, moxford <mo...@gmail.com> wrote:
>
> Exception in thread "main" java.lang.NoSuchMethodError:
> org.quartz.Scheduler.getTrigger(Ljava/lang/String;Ljava/lang/String;)Lorg/quartz/Trigger;
>         at
> org.apache.camel.component.quartz.QuartzComponent.createEndpoint(QuartzComponent.java:134)
>         at
> org.apache.camel.component.quartz.QuartzComponent.createEndpoint(QuartzComponent.java:54)
>
> Looks like the "getTrigger()" call now takes a TriggerKey instead of a pair
> of string params.
> I just checked the tip out of SVN and did not see a fix.
>
> Offending line from Camel QuartzComponent.class:
> trigger = getScheduler().getTrigger(*name, group*);
>
> Scheduler.class from Quartz 2.1.7
>     /**
>      * Get the <code>{@link Trigger}</code> instance with the given key.
>      *
>      * <p>The returned Trigger object will be a snap-shot of the actual
> stored
>      * trigger.  If you wish to modify the trigger, you must re-store the
>      * trigger afterward (e.g. see {@link #rescheduleJob(TriggerKey,
> Trigger)}).
>      * </p>
>      */
>     Trigger getTrigger(*TriggerKey triggerKey*)
>         throws SchedulerException;
>
> Is anyone working on this?
>
> Thanks!
>
> -mox
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/camel-quartz-2-10-4-against-quartz-2-1-7-bug-tp5730615.html
> Sent from the Camel Development mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen