OpenJPA
  1. OpenJPA
  2. OPENJPA-125

OpenJPA-specific metadata cannot be specified in XML descriptors

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: 0.9.0, 0.9.6, 0.9.7
    • Fix Version/s: None
    • Component/s: jpa
    • Labels:
      None

      Description

      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.

        Issue Links

          Activity

          Patrick Linskey created issue -
          Patrick Linskey made changes -
          Field Original Value New Value
          Component/s jpa [ 12311304 ]
          Priority Critical [ 2 ]
          Hide
          Evan Ireland added a comment -

          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.

          Show
          Evan Ireland added a comment - 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.
          Patrick Linskey made changes -
          Affects Version/s 1.0.0 [ 12312341 ]
          Patrick Linskey made changes -
          Affects Version/s 0.9.6 [ 12312342 ]
          Fix Version/s 1.0.0 [ 12312341 ]
          Affects Version/s 1.0.0 [ 12312341 ]
          Affects Version/s 0.9.0 [ 12312343 ]
          Affects Version/s 0.9.7 [ 12312340 ]
          Patrick Linskey made changes -
          Link This issue blocks OPENJPA-87 [ OPENJPA-87 ]
          Patrick Linskey made changes -
          Link This issue is related to OPENJPA-204 [ OPENJPA-204 ]
          David Ezzio made changes -
          Assignee David Ezzio [ dezzio ]
          Craig L Russell made changes -
          Fix Version/s 1.1.0 [ 12312344 ]
          Fix Version/s 1.0.0 [ 12312341 ]
          Hide
          Stefan Hansel added a comment -

          This would also help migrations from kodo-JDO to OpenJPA, since 'old' .jdo and .mapping files just had to be transformed into a new file. And without all the custom extension this wouldn't work.

          Show
          Stefan Hansel added a comment - This would also help migrations from kodo-JDO to OpenJPA, since 'old' .jdo and .mapping files just had to be transformed into a new file. And without all the custom extension this wouldn't work.
          Hide
          Patrick Linskey added a comment -

          Deferring yet again. Hopefully, we can get this into JPA 2.0.

          Show
          Patrick Linskey added a comment - Deferring yet again. Hopefully, we can get this into JPA 2.0.
          Patrick Linskey made changes -
          Fix Version/s 1.2.0 [ 12313102 ]
          Fix Version/s 1.1.0 [ 12312344 ]
          Hide
          Michael Dick added a comment -

          Moving new features to next release

          Show
          Michael Dick added a comment - Moving new features to next release
          Michael Dick made changes -
          Fix Version/s 1.2.0 [ 12313102 ]
          Fix Version/s 1.3.0 [ 12313326 ]
          Donald Woods made changes -
          Fix Version/s 2.0.0 [ 12314019 ]
          Donald Woods made changes -
          Fix Version/s 1.3.0 [ 12313326 ]
          Fix Version/s 2.0.0 [ 12314019 ]

            People

            • Assignee:
              David Ezzio
              Reporter:
              Patrick Linskey
            • Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:

                Development