[
https://issues.apache.org/jira/browse/JDO-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513216#comment-17513216
]
Andy Jefferson commented on JDO-806:
------------------------------------
Just a question why we (currently) have XSD XMLNS for a jdo XML file as
{{<jdo xmlns="http://xmlns.jcp.org/xml/ns/jdo/jdo"}}
{{ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"}}
{{ xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/jdo/jdo
https://db.apache.org/jdo/xmlns/jdo_3_2.xsd"; version="3.2">}}
and not
{{<jdo xmlns="https://db.apache.org/jdo/xmlns/jdo"}}
{{ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"}}
{{ xsi:schemaLocation="https://db.apache.org/jdo/xmlns/jdo
https://db.apache.org/jdo/xmlns/jdo_3_2.xsd"; version="3.2">}}
It seemingly makes no difference to XML validation in an IDE (e.g Eclipse), but
why burden the user with having to think where to put xmlns.jcp.org (that this
API doesn't use, nor is maintained) and where to put db.apache.org ?
For reference, Jakarta Persistence uses jakarta.ee for XMLNS as well as
xsi:schemaLocation
> 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
> Affects Versions: JDO 3.2
> Reporter: Michael Bouschen
> Priority: Major
> Fix For: JDO 3.3
>
>
> 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.1#820001)
