[jira] [Resolved] (BATCHEE-38) readOnly mode is broken on a few containers

["Romain Manni-Bucau (JIRA)" <ji...@apache.org>]

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

Romain Manni-Bucau resolved BATCHEE-38.
---------------------------------------
    Resolution: Fixed

resolving since work has been done and it should appear on the release note, other issues need to be opened to continue the work on that probably

> readOnly mode is broken on a few containers
> -------------------------------------------
>
>                 Key: BATCHEE-38
>                 URL: https://issues.apache.org/jira/browse/BATCHEE-38
>             Project: BatchEE
>          Issue Type: Bug
>          Components: jbatch-servlet
>    Affects Versions: 0.1-incubating
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>            Priority: Critical
>             Fix For: 0.4-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 classpath.



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