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)) |
|||
Line 16: | Line 16: | ||
*JPA 2.0 meta-model generation (Shaun) | *JPA 2.0 meta-model generation (Shaun) | ||
**Probably want incremental generation (on commits) | **Probably want incremental generation (on commits) | ||
− | **Talk to Michael O'Brian and Peter about serialization | + | **Talk to Michael O'Brian and Peter about serialization (set up meeting, incremental generation) |
+ | **What happens when the A processor regens, does it clean up. | ||
+ | **We could tie into refactoring and update queries to point to new metamodel content | ||
**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 | ||
**Use EL to generate the source code (send an email to Peter) | **Use EL to generate the source code (send an email to Peter) |
Revision as of 10:47, 14 July 2009
Contents
Dali 3.0 Design Meetings
July 13-14th, 2009
Attendees: Shaun, Neil, Karen, Brian, Paul, Tran
Agenda
Open design issues (UI and model)
- UI and model for JPA 2.0 Id (Paul)
- Generic JPA is slightly different case than EL
- Generic - source only case, private in foo; - default to Basic mapping in our UI: M-1 default is error with Id
- EclipseLink - default 1:1 makes interpretation difficult
- Is option 2 possible, lets consider further? If not, what are the possible solutions, Option 3 - Lobby spec committee for Derived Id.
- Generic JPA is slightly different case than EL
- JPA 2.0 meta-model generation (Shaun)
- Probably want incremental generation (on commits)
- Talk to Michael O'Brian and Peter about serialization (set up meeting, incremental generation)
- What happens when the A processor regens, does it clean up.
- We could tie into refactoring and update queries to point to new metamodel content
- Generally annotation processor created, but might be advantage to doing this with the Dali model
- Use EL to generate the source code (send an email to Peter)
- Legacy Platform support (Neil)
- Should we support EclipseLink 1.x in Dali 3.0? Yes - keep everything for now
- Platform version requirements (Paul)
- Platform UI selection (Neil)
- Code Topics
- Conversion to Iterables (Brian)
- Model events/listeners (Brian)
- FindBugs(Brian)
- "2.0" naming and package names
Other Topics
- XML Translator issues
- Need to escalate these issues and determine if support is going to be sufficient moving forward