[
https://issues.apache.org/jira/browse/OPENJPA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474846
]
Evan Ireland commented on OPENJPA-125:
--------------------------------------
I would recommend an XML schema that permits properties (e.g. sets of
name/value pairs)
to be specified at the level of entity classes, persistent fields, and named
queries, e.g.
<entity class="com.example.MyEntity">
<property name="sybase.SpecialEntityProperty" value="..."/>
<field name="myPersistentField">
<property name="sybase.SpecialFieldProperty" value="..."/>
</field>
<query name="myNamedQuery">
<property name="sybase.SpecialQueryProperty" value="..."/>
</query>
</entity>
I would suggest keeping the schema this simple. We have found that properties
at these
three levels to be more than adequate for vendor-specific customization of O/R
mapping.
> OpenJPA-specific metadata cannot be specified in XML descriptors
> ----------------------------------------------------------------
>
> Key: OPENJPA-125
> URL: https://issues.apache.org/jira/browse/OPENJPA-125
> Project: OpenJPA
> Issue Type: New Feature
> Components: jpa
> Reporter: Patrick Linskey
> Priority: Critical
>
> OpenJPA includes a number of annotations that extend the behavior of the JPA
> specification. Currently, these annotations cannot be specified in an XML
> descriptor. We must create an XSD that allows XML-based configuration of
> these settings.
> Additionally, to address OPENJPA-87, we should come up with a good story for
> when only spec-level XML is used and OpenJPA annotations are also used.
> Currently, as reported in OPENJPA-87, such a configuration causes us to
> ignore the OpenJPA annotations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
