Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Dali/Juno/JPAMetadataConversion"

< Dali‎ | Juno
(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: [feature name] =
+
= Functional Specification: [JPA Metadata Conversion] =
  
[enter bug location here]  
+
[https://bugs.eclipse.org/138622 bug 138622]- Convert annotated JPA metadata to orm.xml
  
 
== Document History  ==
 
== Document History  ==
{|{{BMTableStyle}}
+
 
|-{{BMTHStyle}}
+
{|
! Date
+
! Author
+
! Version Description & Notes
+
 
|-
 
|-
!
+
! Date
!
+
! Author
!
+
! Version Description &amp; Notes
 +
|-
 +
! 06/16/2011
 +
! Nan Li
 +
! Draft 1 - Added initial prototype and questions we have to collect requirements
 
|}
 
|}
  
 
== Feature overview  ==
 
== Feature overview  ==
  
[Summary]
+
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>
 
+
Goals:
+
 
+
*
+
*
+
 
+
  
 
== References  ==
 
== References  ==
  
[Links to other related information]
+
[http://wiki.eclipse.org/User_Interface_Guidelines User Interface Guidelines]  
  
 +
== Use Cases / Requirements  ==
  
== Use Cases / Requirements ==
+
=== Prototype Option 1 ===

Revision as of 10:52, 17 June 2011

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

References

User Interface Guidelines

Use Cases / Requirements

Prototype Option 1

Back to the top