batchee-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Struberg (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (BATCHEE-38) readOnly mode is broken on a few containers
Date Sun, 10 Aug 2014 20:14:12 GMT

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

Mark Struberg updated BATCHEE-38:
---------------------------------

    Fix Version/s:     (was: 0.2-incubating)
                   0.3-incubating

> 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.3-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.2#6252)

Mime
View raw message