[
https://issues.redhat.com/browse/WFLY-13770?page=com.atlassian.jira.plugi...
]
Cheng Fang commented on WFLY-13770:
-----------------------------------
Looks like this doc section is out of date. It should use the latest schema namespace
({{urn:jboss:domain:batch-jberet:2.0}}), and use {{data-source}} attribute when defining a
jdbc job repository:
{code:xml}
<jboss xmlns="urn:jboss:1.0">
<batch xmlns="urn:jboss:domain:batch-jberet:2.0">
<job-repository>
<jdbc data-source="java:jboss/datasources/ExampleDS"/>
</job-repository>
</batch>
</jboss>
{code}
Create jdbc job repository using deployment descriptors
-------------------------------------------------------
Key: WFLY-13770
URL:
https://issues.redhat.com/browse/WFLY-13770
Project: WildFly
Issue Type: Enhancement
Components: Batch
Affects Versions: 20.0.1.Final
Reporter: Jurij Bernhardt
Assignee: Cheng Fang
Priority: Major
The Example for "new Job Repository"
([
https://docs.wildfly.org/20/Admin_Guide.html#deployment-descriptors]) doesn't work
properly.
{code:xml}
<jboss xmlns="urn:jboss:1.0">
<batch xmlns="urn:jboss:batch-jberet:1.0">
<job-repository>
<jdbc jndi-name="java:jboss/datasources/ExampleDS"/>
</job-repository>
</batch>
</jboss>
{code}
Schema batch-jberet_1_0.xsd alllows only in-memory or named job-repositoryType.
You get the validation exception by using the jdbc example.
It would be useful to improve the batch-jberet integration so that the example given
above would work.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)