openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Austin Dorenkamp (JIRA)" <>
Subject [jira] [Updated] (OPENJPA-2366) provide option to exclude schema name from generated @Table annotation for generated entities
Date Mon, 12 Aug 2013 20:41:47 GMT


Austin Dorenkamp updated OPENJPA-2366:

    Attachment: OPENJPA-2366doc-3.patch

The updated patches have just been attached. In this comment I will briefly walk through the
~TestUseSchemaElement (TUSE) is a new class that test my changes
~ReverseMappingTool (RMT) contains the majority of the changes - including initially setting
the UseSchemaElement (USE) flag. From the RMT class, the USE flag is stored in the ClassMetaData
object where it is eventually retrieved from Annotation/XMLPersistenceMetaDataSerializer (where
it is stored) by the Annotation/XMLPersistenceMappingSerializer. 
~FieldMetaData is a class that the comments in CMD said to update with any changes to CMD
~ReverseMappingToolTask was updated to mirror changes to RMT
~persistence.xml was updated to enable the use of a local derby database in TUSE
> provide option to exclude schema name from generated @Table annotation for generated
> ---------------------------------------------------------------------------------------------
>                 Key: OPENJPA-2366
>                 URL:
>             Project: OpenJPA
>          Issue Type: New Feature
>          Components: jpa
>    Affects Versions: 2.2.0, 2.2.1
>            Reporter: John Mysak
>            Assignee: Austin Dorenkamp
>            Priority: Minor
>         Attachments: OPENJPA-2366-3.patch, OPENJPA-2366doc-3.patch
>   Original Estimate: 2h
>  Remaining Estimate: 2h
> Feature request:
> Provide an option for org.apache.openjpa.jdbc.meta.ReverseMappingTool that will exclude
the schema name for the @Table annotation on generated entities.  For example, if the schema
name is not required and needs to be dynamically specified at deployment time via openjpa.jdbc.Schema.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message