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

Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2017/11/22 15:05:00 UTC

[jira] [Resolved] (KARAF-3875) Karaf scheduler should wrap QuartzException in exported SchedulerException

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

Jean-Baptiste Onofré resolved KARAF-3875.
-----------------------------------------
    Resolution: Fixed

> Karaf scheduler should wrap QuartzException in exported SchedulerException
> --------------------------------------------------------------------------
>
>                 Key: KARAF-3875
>                 URL: https://issues.apache.org/jira/browse/KARAF-3875
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-scheduler
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 4.1.4, 4.2.0, 4.2.0.M1
>
>
> I'd like to be able to use the Scheduler service that is registered. Unfortunately it's not possible because the schedule method on that service throws an org.quartz.Scheduler that is not exported by the Karaf Scheduler bundle.
> Maybe the exception should be wrapped into a new Exception defined by the bundle instead ? Because even if it is re-imported from another bundle I'm guessing there will be problems with class loading because the class instance will be generated from another class loader.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)