[JDO-806] Use apache URL for schemaLocation of JDO XSDs

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: JDO 3.2
• Fix Version/s: JDO 3.2.1
• Component/s: api, specification
• Assignee: Michael Bouschen
• Reporter: Michael Bouschen
• Created: 12/Feb/22 14:03
• Updated: 04/May/22 19:35
• Resolved: 04/May/22 19:35

Description

In JDO 3.2 the schemaLocation of JDO XSDs link to http://xmlns.jcp.org/xml/ns/jdo/<xsd> where <xsd> is one of jdo_3_2.xsd, jdoconfig_3_2.xsd, jdoquery_3_2.xsd, orm_3_2.xsd. It seems that the site http://xmlns.jcp.org/xml/ns is not updated anymore, so it is unlikely that the 3.2 XSDs are available under this URL (see JDO-744).

One idea ist might be to switch to an Apache URL, where we can control the download sites.

This change requires corresponding changes to the specification, api, and tck. Here is a proposed plan to implement:

1. Update the xsds and dtds in the api/resources to change the headers.
2. Update the xsds and dtds in the db.apache.org/jdo/xmlns with the changes.
3. Update the xsds and dtds in the tck with the changes. This step will fail without a corresponding change to the reference implementation.
4. Update the specification with the changes. A partial list of affected sections:
   1. 11.1.4 p. 122
   2. 18.24 p. 261
   3. 18.25 p. 265
   4. 18.26 p. 287, 298
   5. New C.23 Changes since 3.2 p. 404

Open question: should we keep the version number of the xsd and dtd files as 3.2 even though the api, tck, and specification will be updated to 3.2.1? I would say yes, and only change the version number of the files if there is a change to the content of the xsd and/or dtd.

My proposal is: the 3.2.1 version of JDO would still refer to the 3.2 version of the xsd and dtd.

Issue Links

• fixes: JDO-744 XSD/DTD not published for JDO 3.1
• incorporates: JDO-807 Update schema descriptor of JDO Metadata file to use latest 3.2 xsd definition
• links to: GitHub Pull Request #40