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.
DaliMinutes060420
Revision as of 15:25, 20 April 2006 by Unnamed Poltroon (Talk)
Dali M3 Planning Meeting
Attendees: Neil Hauge, Paul Fullbright, Tran Le, Karen Moore, Rick Sapir, Markus Kuppe, Shaun Smith, Brian Vosburgh
Projected Milestone 3: May 12, 2006
Tenatively Planned
- persistence.xml support
- Add persistence ->creates base template for persistence.xml
- Manual synching vs User configurable auto-synching (one of these*) (Paul)
- Validation* (Paul)
- Support for Inheritance (staged approach)
- Single Table inheritance first
- Join
- Usability
- Persistence perspective rearranged
- Re-login to the database, login as required (Tran or Neil)
- Priority list to prevent errors for features we don’t yet support
- SecondaryTable error – bug#136379 (Karen)
- Add EmbeddedId annotation – w/out problems support (Karen)
- Priority refactoring
- Moving to tabbed property panes?
- UI test conversion?
- Model build order
Feature Priority Results
Suggestions from the community: Work toward the spec examples.
High
- Support for Inheritance (staged approach) Single Table inheritance first
- persistence.xml support
- Add persistence ->creates base template for persistence.xml
- Manual synching vs User configurable auto-synching (one of these*)
- Validation*
- Support for IdClass, associated problems (put problems on the IdClass annotation)
- EmbeddedID, associated problems
- Usability
- Re-login to the database, login as required
- Persistence perspective rearranged
- Complete sequence support (usability)
- Quick fixes for base cases (eventually support anything with a choice of values)
- Priority list to prevent errors for features we don’t yet support
- Could convert applicable errors to warnings if we know they could be applied incorrectly
- Schema/Catalog annotation – how can we avoid errors when this is specified – warning to say we are not validating or hook into problems with existing model support
- Priority refactoring
- UI test conversion?
- UI Binding (Markus investigating)
- Tabbed Property Pane
- Model build
- SecondaryTable model support (allow selecting fields from secondary tables)
- Temporal (also should be in entity gen / ddl gen)
- MapKey
Medium
- Java Persistence Project creation
- Moving to WTP Facets
- Moving to WTP Validation Framework
- Persistence.xml
- Rich UI Editing
- Extended XML editing
- Finish translation support (ensure all applicable strings are externalized)
- Complete sequence support (usability)
- Integration with Java refactoring - Need use cases for what to do…Log in existing ER (Shaun to start this off) 136333(JDT dependent bug)
- Lob
- Enumerated
Low
- Cascade array
- Generator Library
- Callbacks support *
- Schema/Catalog annotation
Target Compatibility: Eclipse 3.2RC3, WTP1.5RC3
Notes:
- SequenceGenerators are only support when linked with an ID.