[
https://issues.apache.org/jira/browse/JDO-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17491450#comment-17491450
]
Craig L Russell commented on JDO-806:
-------------------------------------
We could use something like
[https://db.apache.org/jdo/xmlns/jdo_3_2.xsd]
There is no default rendering of xsd or dtd files in browsers, but a program
should be able to handle them and we should be able to figure out how to
publish them.
In any event, the JDO Implementation will cache the known files locally so it
doesn't have to load them except possibly at workspace startup, if then.
> 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
>
> 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 message was sent by Atlassian Jira
(v8.20.1#820001)
