batchee-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Romain Manni-Bucau (JIRA)" <>
Subject [jira] [Commented] (BATCHEE-38) readOnly mode is broken on a few containers
Date Sat, 10 May 2014 22:05:00 GMT


Romain Manni-Bucau commented on BATCHEE-38:

we should add a flag but not forcing it to be false. Please restore previous code adding a
system property or batchee property to force the value.

Side note: this is not portable but aligned on JVM behavior (URLClassLoader) so think it is
ok as default even if broken on several containers using very customized classloaders.


> readOnly mode is broken on a few containers
> -------------------------------------------
>                 Key: BATCHEE-38
>                 URL:
>             Project: BatchEE
>          Issue Type: Bug
>          Components: jbatch-servlet
>    Affects Versions: 0.1-incubating
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>            Priority: Critical
>             Fix For: 0.2-incubating
> currently the JBatchServletInitializer queries whether there are batch job xmls on the
classpath in an illegal way with
> classLoader.getResources("META-INF/batch-jobs")
> but this will always return zero as it is not defined in getResources that a directory
is a 'resource'. Of course performing
> classLoader.getResources("META-INF/batch-jobs/myjob.xml") will return something....
> Means there is no way to switch to a generic read-only configuration in a portable way.

> What we can do is to allow to only control batches which have the proper job xml in the

This message was sent by Atlassian JIRA

View raw message