You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Jonathan Anstey (JIRA)" <ji...@apache.org> on 2015/07/10 16:20:05 UTC

[jira] [Resolved] (CAMEL-8950) Injected Quartz2 scheduler doesn't have access to CamelContext in jobs

     [ https://issues.apache.org/jira/browse/CAMEL-8950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Anstey resolved CAMEL-8950.
------------------------------------
    Resolution: Fixed

https://git1-us-west.apache.org/repos/asf?p=camel.git;a=commit;h=4fc73b4cde1b0f6e8d57e4a9c32377e118dcb69e

> Injected Quartz2 scheduler doesn't have access to CamelContext in jobs
> ----------------------------------------------------------------------
>
>                 Key: CAMEL-8950
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8950
>             Project: Camel
>          Issue Type: Bug
>    Affects Versions: 2.15.2
>            Reporter: Jonathan Anstey
>            Assignee: Jonathan Anstey
>             Fix For: 2.16.0, 2.15.3
>
>
> Currently if you inject a scheduler the CamelContext won't be available for jobs to access. When the scheduler is created automatically, the context is added to the quartz scheduler context so the jobs can access it:
> quartzContext.put(QuartzConstants.QUARTZ_CAMEL_CONTEXT + "-" + camelContextName, getCamelContext());



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)