Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Job versioning does not appear to be supported in JBeret #278

Open
idursto opened this issue Dec 6, 2022 · 1 comment
Open

Job versioning does not appear to be supported in JBeret #278

idursto opened this issue Dec 6, 2022 · 1 comment

Comments

@idursto
Copy link

idursto commented Dec 6, 2022

Somewhat new to JBeret and JSR-352, but after setting things up and debugging it does not appear the version columns are populated based on what you have set within your job...

My Example job:

<job id="test" restartable="#{jobParameters['restartable']}?:true" 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"> ... etc ...

And the JdbcRepository inserts I debugged down to:

preparedStatement.setString(2, jobInstance.getApplicationName());

preparedStatement.setString(4, BatchUtil.propertiesToString(jobExecution.getJobParameters()));

Am I missing something in my settup or is this just something that is not in scope of what is supported within JBeret? I dont feel like it would be too difficult to persist the version from the Job XML down the repository would it?

Any help is appreciated...

@chengfang
Copy link
Contributor

version can be safely ignored. Initially it was intended to track different versions of job data, but is not implemented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants