How do I start a job, when the job name is not known at deployment time? - wildfly

Question

I'm trying to start a batch job, which isn't known at deployment time. (Admin users can define their own jobs via rest-api)
I'm calling:
JobOperator jobOperator = BatchRuntime.getJobOperator();
-- > Class org.wildfly.extension.batch.jberet.deployment.JobOperatorService -
Which dosn't allow to start unknown jobs.
Javadoc says:
* Note that for each method the job name, or derived job name, must exist for the deployment. The allowed job names and
* job XML descriptor are determined at deployment time.
How can i start jobs that are not determined at deployment?
Thanks in advance

Answer 1

You can have some conventions in your batch job naming, so that it is kind of known at deployment time to bypass the deployment-time validation. For instance, you can package a placeholder job in your application:
<?xml version="1.0" encoding="UTF-8"?>
<job id="submitted-job" xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/jobXML_1_0.xsd" version="1.0">
<!-- this job is defined and submitted dynamically by the client -->
</job>
At runtime, the admin can then dynamically fill in the job content.