[
https://issues.apache.org/jira/browse/OPENJPA-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved OPENJPA-1971.
--------------------------------------
Resolution: Fixed
Already fixed on master: Done under OPENJPA-2081 (3f8d02190, on master).
XMLPersistenceMetaDataParser.java:618-630 loads extendable-orm.xsd and
openjpa-orm.xsd, and ref_guide_meta.adoc:365 documents them. Closing; please
reopen if this still happens with OpenJPA 4.x.
> Provide XML-based configuration for OpenJPA's custom metadata and mapping
> extensions
> ------------------------------------------------------------------------------------
>
> Key: OPENJPA-1971
> URL: https://issues.apache.org/jira/browse/OPENJPA-1971
> Project: OpenJPA
> Issue Type: New Feature
> Components: competitive, jpa, usability
> Affects Versions: 2.2.0
> Reporter: Jeremy Bauer
> Assignee: Dianne E. Richards
> Priority: Major
> Attachments: supported_annotations.pdf, supported_annotations.pdf
>
>
> Context: The JPA specification includes many annotations for the
> specification of metadata and mapping information within Java classes. In
> addition, the spec provides a means to supply the same information within XML
> configuration files (orm.xml). One primary benefit of XML config files is it
> allows modification of the ORM information without needing to recompile the
> source code.
> OpenJPA has many custom metadata and mapping annotations that can be used to
> provided functionality beyond the JPA specification. However, these
> extensions are available only through annotations. There is currently no
> means to specify the metadata or mapping extensions via XML. We've had
> several requests for this capability, but it hasn't seen much/any activity.
>
> Task:
> 1) Understand OpenJPA's annotation extensions.
> 2) Determine which annotations make sense to provide in XML configuration
> 3) Design a schema for the XML-based configuration file (openjpa-orm.xml?)
> 4) Creating metadata and mapping parsers for the new XML mapping file
> 5) Wire the new parsers into the existing code path.
> 6) Provide adequate jUnit tests for the new function.
> Mentor: techhusky at gmail dot com
> Complexity: moderate
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
