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 "Dali/Juno/JPAMetadataConversion"
(New page: = Functional Specification: [feature name] = [enter bug location here] == Document History == {|{{BMTableStyle}} |-{{BMTHStyle}} ! Date ! Author ! Version Description & Notes |- ! ! ! ...) |
|||
Line 1: | Line 1: | ||
− | = Functional Specification: [ | + | = Functional Specification: [JPA Metadata Conversion] = |
− | [ | + | [https://bugs.eclipse.org/138622 bug 138622]- Convert annotated JPA metadata to orm.xml |
== Document History == | == Document History == | ||
− | {| | + | |
− | + | {| | |
− | + | ||
− | + | ||
− | + | ||
|- | |- | ||
− | ! | + | ! Date |
− | ! | + | ! Author |
− | ! | + | ! Version Description & Notes |
+ | |- | ||
+ | ! 06/16/2011 | ||
+ | ! Nan Li | ||
+ | ! Draft 1 - Added initial prototype and questions we have to collect requirements | ||
|} | |} | ||
== Feature overview == | == Feature overview == | ||
− | + | The purpose of this feature is to provide the ability to generate mapping files from the annotated sources so that users can get different behaviors by configuring generated mapping files without touching their well configured sources. Considering our users will be developers, tradeoffs would be made based on this when<br> | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
== References == | == References == | ||
− | [ | + | [http://wiki.eclipse.org/User_Interface_Guidelines User Interface Guidelines] |
+ | == Use Cases / Requirements == | ||
− | == | + | === Prototype Option 1 === |
Revision as of 10:52, 17 June 2011
Contents
Functional Specification: [JPA Metadata Conversion]
bug 138622- Convert annotated JPA metadata to orm.xml
Document History
Date | Author | Version Description & Notes |
---|---|---|
06/16/2011 | Nan Li | Draft 1 - Added initial prototype and questions we have to collect requirements |
Feature overview
The purpose of this feature is to provide the ability to generate mapping files from the annotated sources so that users can get different behaviors by configuring generated mapping files without touching their well configured sources. Considering our users will be developers, tradeoffs would be made based on this when