Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "DaliMinutes060419"

 
m (Dali Status/Planning meeting - 2006-04-19 | 15:00-16:30UTC)
Line 1: Line 1:
 
=Dali Status/Planning meeting - 2006-04-19 | 15:00-16:30UTC=
 
=Dali Status/Planning meeting - 2006-04-19 | 15:00-16:30UTC=
  
Attendees: Neil Hauge, Brian Vosburgh, Markus Kuppe, Karen Moore, Max Anderson, Tran Le, Christian Ernst, Shaun Smith
+
Attendees: Neil Hauge, Brian Vosburgh, Markus Kuppe, Karen Moore, Max Andersen, Tran Le, Christian Ernst, Shaun Smith
  
 
==M2 Review and general project status==
 
==M2 Review and general project status==

Revision as of 16:34, 19 April 2006

Dali Status/Planning meeting - 2006-04-19 | 15:00-16:30UTC

Attendees: Neil Hauge, Brian Vosburgh, Markus Kuppe, Karen Moore, Max Andersen, Tran Le, Christian Ernst, Shaun Smith

M2 Review and general project status

Completed functionality

  • Entity generation from Table – phase 2 (1-M, M-1, M-M, Java code conventions)
  • Multiple JoinColumns support for relationship mappings
  • Embedded, Context sensitive help - Dali User Guide
  • Automated Build is pretty much there.
  • Now building against WTP 1.5M6 (jump to 1.5 stream has been made)

Work in progress

  • persistence.xml support
    • Project creation wizard
  • Refactoring
    • UI Binding
    • Model build sequence
    • Tests


Feature Priority Results

Suggestions from the community: Work toward the spec examples.

High

  • persistence.xml support
  • Support for IdClass, EmbeddedID
  • 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
    • Tabbed Property Pane
  • SecondaryTable model support (allow selecting fields from secondary tables)
  • Temporal (also should be in entity gen / ddl gen)
  • MapKey

Medium

  • Finish translation support (ensure all applicable strings are externalized)
  • Complete sequence support (usability)
  • Support for Inheritance (staged approach) Single Table inheritance first
  • 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


Backlog

  • Extensions / model refactoring
    • Coping with more than one annotation per item
  • Moving to Platform frameworks
    • Extending the java properties
    • Moving to tabbed property pane
  • Support for Inheritance *(community support)
  • Support for IdClass, EmbeddedID
  • Callbacks support *
  • Generator Library
  • Text based support for query entry
  • Extension investigation/refactoring/prototyping
  • Support for additional EJB3 mapping annotations
    • SecondaryTable(s) *
    • Lob
    • Temporal
    • Enumerated
    • MapKey
    • Schema/Catalog annotation support
  • Annotation Value completion (Dependency on APT)
  • Enhanced outline view (quick view of entity config)
  • General usability enhancements
  • Integration with Java refactoring - Need use cases for what to do…Log in ER
    • Quick fixes


Move to WTP

  • This has been discussed with the WTP PMC and we are looking at a likely move date of early May.

Back to the top