Dali Weekly Meeting

Agenda

Should we have a base MOXy Platform to help with JAXB wizards, Library Validation, model validation, etc, if it doesn't support any MOXy specific annotations or the MOXy mapping file?
- XJC should be shipped with Eclipse
- Users may need to have XJC on classpath anyway to support dynamic JAXB
- Shaun and others are in favor of the light MOXy platform
Performance/UI responsiveness: What should we do about building JPA projects
- May want to provide a preference -eg Map dependent JARs- (default: on) in maintenance for a quick fix
- IN new wizard, default pref to off for new projects
Any validation we might be missing for XmlAnyAtrribute and XmlMixed
- Blaise not here today

JAXB Demo for Blaise
- Schema/namespace selection
- Schema related code completion and validation
- Explorer Content
- Type level completion and validation
- Feedback
  - copy schema into project when doing class gen
  - need a way to make these things portable
  - validation for public field and public property have the same name
JAXB context
- What should the priority be for different types of JAXB context definition? What are most users using?
Top of the priority list
- transitively referenced, see also, xmlelement annotation type=foo.class, foo.class should be included in the context
- root elements
Next
- jaxb.index
- create jaxb.index in the proj wizard, and outside

Shaun will continue to investigate WAB, bundle root changes, etc.
OSGi JPA spec support - need to investigate this to see what things we may need to support for OSGi
Allow for sync options for the persistence.xml at the project level