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 "Minutes of the JEE 5 Working Group meeting Mar 22, 2007"
(→Minutes) |
|||
| Line 14: | Line 14: | ||
=== Minutes === | === Minutes === | ||
| − | Meeting | + | Meeting was very short due to incorrect call info therefore low attendance. |
Only a few managed to find their ways to the call. We went over the JEE5 scenarios for WTP2.0. These use cases will be posted on the wiki. With only few weeks of development time remaining for the M6 we should really focus our efforts. | Only a few managed to find their ways to the call. We went over the JEE5 scenarios for WTP2.0. These use cases will be posted on the wiki. With only few weeks of development time remaining for the M6 we should really focus our efforts. | ||
Latest revision as of 10:02, 3 April 2007
Contents
Teleconference on JEE 5 Support in WTP Mar 22, 2007
Attendance
- Naci Dai - Eteration
- Neil Hauge - Oracle
- Dave Gorton - BEA
- Rob Frost - BEA
Agenda
- Review Priorities
ACTION ITEMS
Minutes
Meeting was very short due to incorrect call info therefore low attendance.
Only a few managed to find their ways to the call. We went over the JEE5 scenarios for WTP2.0. These use cases will be posted on the wiki. With only few weeks of development time remaining for the M6 we should really focus our efforts.
At this point I believe our priorities are (in the order of importance): 1) Runtime support for JEE5 modules - If we have a JEE5 module (Web 2.5/EJB3/EAR) we should be able to run it on servers (Tomcat/Geronimo/Glassfish). Having the server adapters ready to support these modules will also be important, especially for EJB3 and EAR5.
2) JEE 5 Model extensibility - This issue has been addressed by Chuck.
3) Editing and Tools support: I do not believe our editors(and tools like wizards etc.) will be ready to have full JEE5 support by 2.0. This should be a post 2.0 task.