Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Talk:EclipseLink/DesignDocs/214519"
(New page: Everything in @ELTable should be optional and the contents should override that of @Table.<BR> What about a calling the annotation @TableExt (Ext for extension) or @TableOverrides or some...) |
(→ELTable: new section) |
||
Line 3: | Line 3: | ||
[[User:Gordon.yorke.oracle.com|Gordon Yorke]] 13:58, 1 October 2010 (UTC) | [[User:Gordon.yorke.oracle.com|Gordon Yorke]] 13:58, 1 October 2010 (UTC) | ||
---- | ---- | ||
+ | |||
+ | == ELTable == | ||
+ | |||
+ | --[[User:Douglas.clarke.oracle.com|Doug]] 13:58, 5 October 2010 (UTC) | ||
+ | My first impression is that I am not fond of duplicating standard JPA annotations with EL prefix if it can be avoided. | ||
+ | * Is this really a table scoped feature or is it a PU level config that should be applied to all tables (Note: Have not read the original request). | ||
+ | * PU Config | ||
+ | ** PU Property | ||
+ | ** Even if it is a table level config it would be nice to configure it once for all tables using a PU property | ||
+ | * eclipselink-orm.xml would allow an additional optional attribute in <table .../> | ||
+ | * Annotation | ||
+ | ** If it is required at a per table level should we consider only supporting this using an eclipselink-orm.xml? | ||
+ | ** If we believe an annotation is essential is there a better pattern to extend @Table without duplicating it? |
Revision as of 09:58, 5 October 2010
Everything in @ELTable should be optional and the contents should override that of @Table.
What about a calling the annotation @TableExt (Ext for extension) or @TableOverrides or something else?
Gordon Yorke 13:58, 1 October 2010 (UTC)
ELTable
--Doug 13:58, 5 October 2010 (UTC) My first impression is that I am not fond of duplicating standard JPA annotations with EL prefix if it can be avoided.
- Is this really a table scoped feature or is it a PU level config that should be applied to all tables (Note: Have not read the original request).
- PU Config
- PU Property
- Even if it is a table level config it would be nice to configure it once for all tables using a PU property
- eclipselink-orm.xml would allow an additional optional attribute in <table .../>
- Annotation
- If it is required at a per table level should we consider only supporting this using an eclipselink-orm.xml?
- If we believe an annotation is essential is there a better pattern to extend @Table without duplicating it?