You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Michael Bouschen (Jira)" <ji...@apache.org> on 2022/05/04 19:36:00 UTC
[jira] [Resolved] (JDO-806) Use apache URL for schemaLocation of JDO XSDs
[ https://issues.apache.org/jira/browse/JDO-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Bouschen resolved JDO-806.
----------------------------------
Resolution: Fixed
Merge PR #1 into the spec repository
> Use apache URL for schemaLocation of JDO XSDs
> ---------------------------------------------
>
> Key: JDO-806
> URL: https://issues.apache.org/jira/browse/JDO-806
> Project: JDO
> Issue Type: Improvement
> Components: api, specification
> Affects Versions: JDO 3.2
> Reporter: Michael Bouschen
> Assignee: Michael Bouschen
> Priority: Major
> Fix For: JDO 3.2.1
>
>
> 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:
> # Update the xsds and dtds in the api/resources to change the headers.
> # Update the xsds and dtds in the db.apache.org/jdo/xmlns with the changes.
> # Update the xsds and dtds in the tck with the changes. This step will fail without a corresponding change to the reference implementation.
> # Update the specification with the changes. A partial list of affected sections:
> ## 11.1.4 p. 122
> ## 18.24 p. 261
> ## 18.25 p. 265
> ## 18.26 p. 287, 298
> ## 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.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)