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.
Difference between revisions of "DaliMeetingMinutes20090714"
(→Open design issues (UI and model)) |
m (→Open design issues (UI and model)) |
||
| Line 9: | Line 9: | ||
===Open design issues (UI and model)=== | ===Open design issues (UI and model)=== | ||
| − | *UI for JPA 2.0 Id (Paul) | + | *UI and model for JPA 2.0 Id (Paul) |
*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 | ||
Revision as of 10:50, 13 July 2009
Contents
Dali 3.0 Design Meetings
July 13-14th, 2009
Attendees:
Agenda
Open design issues (UI and model)
- UI and model 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
- Legacy Platform support (Neil)
- Should we support EclipseLink 1.x in Dali 3.0?
- Platform version requirements (Paul)
- Platform UI selection (Neil)
- Code Topics
- Conversion to Iterables (Brian)
- Model events/listeners (Brian)
- FindBugs(Brian)
Other Topics
- XML Translator issues
- Need to escalate these issues and determine if support is going to be sufficient moving forward