persistence_1_0.xsd is missing

• Key: OPENJPA-57
• Type: Improvement
• Status: Resolved
• Resolution: Won't Fix
• Priority: Major
• Assignee: Unassigned
• Reporter: Stefan Arentz
• Fix Version/s: 0.9.7

Description

It seems to be common that JPA providers include persistence_1_0.xsd in one of the distribution jars. I'm not sure if this is according to the spec but some tools such as Spring already depend on that behaviour.

This is probably mostly relevant for using JPA in a J2SE environment as I think the xsd is probably provided by the app server.

Discussion on the Spring forum about this:

 http://forum.springframework.org/showthread.php?t=26209&highlight=persistence_1_0.xsd

 S.

Comments

[David Jencks]

Is there some reason to think that apache has a license to redistribute this file? The copy I found at

http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd

appeared to say nothing whatsoever about redistribution but following the link at the bottom of the page

http://java.sun.com/xml/ns/persistence/

to

http://www.sun.com/termsofuse.html

I found this:

10.4 Unless explicitly stated herein, nothing in these Terms shall be construed as conferring any license to intellectual property rights, whether by estoppel, implication, or otherwise. Permission is granted to display, copy, distribute and download Content owned by Sun on this Website provided that: (a) the copyright notice pertaining to the Content remains, and a permission notice (e.g., "Used with permission") is added to such Content; (b) the use of such Content is solely for personal and non-commercial use; (c) such Content will not be copied or posted on any networked computer or published in any medium, except as explicitly permitted by valid permission or license covering such materials; and (d) no modifications are made to such Content. This permission terminates automatically without notice if You breach any of the terms or conditions in this Section 10.4. Upon termination, You must immediately destroy any downloaded and/or printed Content.

which appears to me to quite definitely prohibit redistributing the schema without written permission.

[Patrick Linskey]

If the user does not specify an XSD, OpenJPA doesn't require that the XSD is present to parse files. Since OpenJPA does not need the file to be around, and the legality of distributing it is in question, I'm marking this as will-not-fix. The linked-to Spring forum issue seems to be due to a dependency in the Spring codebase; let's let them decide whether they want to ship the XSD or make it optional.