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 "DaliMeetingMinutes20090714"
(→Open design (UI and model) issues) |
(→Open design issues (UI and model)) |
||
| Line 12: | Line 12: | ||
*JPA 2.0 meta-model generation (Shaun) | *JPA 2.0 meta-model generation (Shaun) | ||
**Generally annotation processor created, but might be advantage to doing this with the Dali model | **Generally annotation processor created, but might be advantage to doing this with the Dali model | ||
| − | *Conversion to Iterables (Brian) | + | *Code Topics |
| + | **Conversion to Iterables (Brian) | ||
| + | **Model events/listeners (Brian) | ||
| + | **FindBugs(Brian) | ||
*Legacy Platform support (Neil) | *Legacy Platform support (Neil) | ||
**Should we support EclipseLink 1.x in Dali 3.0? | **Should we support EclipseLink 1.x in Dali 3.0? | ||
Revision as of 21:30, 9 July 2009
Contents
Dali 3.0 Design Meetings
July 13-14th, 2009
Attendees:
Agenda
Open design issues (UI and model)
- UI for JPA 2.0 Id (Paul)
- JPA 2.0 meta-model generation (Shaun)
- Generally annotation processor created, but might be advantage to doing this with the Dali model
- Code Topics
- Conversion to Iterables (Brian)
- Model events/listeners (Brian)
- FindBugs(Brian)
- Legacy Platform support (Neil)
- Should we support EclipseLink 1.x in Dali 3.0?
- Platform version requirements (Paul)
- Platform UI selection (Neil)
Other Topics
- XML Translator issues
- Need to escalate these issues and determine if support is going to be sufficient moving forward