Cheng Fang
Cheng Fang
Custom POJO types are not supported in batch property injection. However, you can inject into fields of type java.util.List with a comma-separated values, or java.util.Map with a comma-separated key-value pairs.
JBeret uses CDI to perform the property @Inject. Without knowing the target POJO type, it's hard to do it in JBeret. However, it will be easier to do it in...
Your code path is different from the current version. Which version of JBeret, or which version of WildFly if using JBeret inside WildFly? Can you try the latest version?
Could be related to https://issues.jboss.org/browse/JBERET-191 But issue JBERET-191 is about setting the wrong job instance, not the null job instance. Looks like some problem during deserializaing job execution data from...
job execution data is also cached. I guess in your test server, those job execution data is present in memory and in db too, so there is no need to...
@jamezp WDYT? As a workaround, PurgeBatchlet can always be extended by applications to customize its behavior.
Yeah, PurgeBatchlet should change to non-final. Maybe we can try to introspect `getDelegate()` and if it successfully returns a `JdbcRepository`, then proceed as usual. I don't like having to change...
The following are screenshots related to batch job scheduling: