Jump to: navigation, search

DaliMinutes060420

Revision as of 11:40, 21 April 2006 by Nhauge (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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 (Paul) – 90%
    • Validation (Paul) - 10 days
    • User configurable auto-synching (Paul - time permiting) - 10 days
  • Support for Inheritance (staged approach)
    • Single Table inheritance first (Karen) – 10 days
    • Join (Karen – Time permitting) - 10 days
  • Usability
    • Persistence perspective rearranged (Neil) - 1 day
    • Re-login to the database, login as required (Tran or Neil) - 3 days
  • Priority list to prevent errors for features we don’t yet support
    • SecondaryTable error – bug#136379 (Karen) – 50%
    • Add EmbeddedId annotation – w/out problems support (Karen) - Complete
  • Priority refactoring
    • Moving to tabbed property panes investigation (Karen)
    • UI Binding (Markus investigating)
    • UI test conversion (Karen - time permitting)
  • Support for IdClass and problems (Tran) – 5 days
  • EmbeddedId problems support (Tran) – 3 days
  • Temporal (also should be in entity gen / ddl gen) (Brian) – 5 days
  • https://bugs.eclipse.org/bugs/show_bug.cgi?id=136658 (Brian) – 3 days
  • Entity Gen ER’s (Brian) – 5 days


Feature Priority Results

Suggestions from the community: Work toward the spec examples.

High

  • (M3) Support for Inheritance (staged approach) Single Table inheritance first
  • (M3) persistence.xml support
    • Add persistence ->creates base template for persistence.xml
    • Manual synching vs User configurable auto-synching (one of these*)
    • Validation*
  • (M3)Support for IdClass, associated problems (put problems on the IdClass annotation)
  • (M3)EmbeddedID, associated problems
  • Usability
    • (M3)Re-login to the database, login as required
    • (M3)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
    • (M3)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
    • (M3)UI test conversion
    • (M3)UI Binding (Markus investigating)
    • Tabbed Property Pane
    • Model build
  • (M3)SecondaryTable model support (allow selecting fields from secondary tables)
  • (M3)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.