jakartaee / jakartaee/specifications

Missing wildcard characters in Jakarta Batch spec documents

Open
#851 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
140
Forks
91
Avg merge
10d 19h
Merged PRs (30d)
6

Description

All versions of the Jakarta Batch spec have an error everywhere it discusses wildcard characters in both the HTML and PDF versions:
https://github.com/jakartaee/specifications/blob/71478f8694b1fb17b3cd58de6eef3103fc918075/batch/2.0/jakarta-batch-spec-2.0.pdf
https://github.com/jakartaee/specifications/blob/71478f8694b1fb17b3cd58de6eef3103fc918075/batch/2.0/jakarta-batch-spec-2.0.html#L2406-L2408
https://github.com/jakartaee/specifications/blob/71478f8694b1fb17b3cd58de6eef3103fc918075/batch/2.0/jakarta-batch-spec-2.0.html#L3286-L3288
https://github.com/jakartaee/specifications/blob/71478f8694b1fb17b3cd58de6eef3103fc918075/batch/2.0/jakarta-batch-spec-2.0.html#L3342-L3344
https://github.com/jakartaee/specifications/blob/71478f8694b1fb17b3cd58de6eef3103fc918075/batch/2.0/jakarta-batch-spec-2.0.html#L3399-L3401
https://github.com/jakartaee/specifications/blob/71478f8694b1fb17b3cd58de6eef3103fc918075/batch/2.0/jakarta-batch-spec-2.0.html#L3455-L3457

For reference, the associated section of the JSR-352 spec reads:

> Specifies an exit status to match to the current next element. It must be a valid XML
> string value. Wildcards of "\*" and "?" may be used. "\*" matches zero or more
> characters. "?" matches exactly one character. It must match an exit status value in
> order to have effect. This is a required attribute.
> [JSR-352](https://jcp.org/aboutJava/communityprocess/final/jsr352/index.html)

It looks like an issue with the original parsing/processing of the \* and ? characters used for the wildcards

Contributor guide

No contributing guide indexed for this repository

Research direction

Compare the linked Jakarta Batch 2.0 HTML passages and PDF with the quoted JSR-352 wording, then locate the source or processing step shared by the affected spec versions. Correct the wildcard characters in the source so both generated HTML and PDF documents display them, and verify each listed occurrence.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.