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 "EclipseLink/Development/DevMeetings"
< EclipseLink | Development
m (→DBWS) |
m (→DBWS) |
||
| Line 115: | Line 115: | ||
* Feature: [http://wiki.eclipse.org/EclipseLink/Development/DBWS/ParseDDLforMetadata Parse DDL to extract database metadata] | * Feature: [http://wiki.eclipse.org/EclipseLink/Development/DBWS/ParseDDLforMetadata Parse DDL to extract database metadata] | ||
** This is a change in the way we access type metadata, that will cover off the following enhancement requests | ** This is a change in the way we access type metadata, that will cover off the following enhancement requests | ||
| − | *** Sprints 6&7: Advanced Oracle types, PL/SQL types using %ROWTYPE% and %TYPE% macros, completed | + | *** [http://wiki.eclipse.org/EclipseLink/Development/DBWS/ParseDDLSprints Sprints 6&7]: Advanced Oracle types, PL/SQL types using %ROWTYPE% and %TYPE% macros, completed |
| − | *** 325124 | + | *** 325124, 339721 Provide support for strongly typed package REF CURSOR |
| − | + | ||
*** 339909 - DBWS should support optional argument queries | *** 339909 - DBWS should support optional argument queries | ||
*** 329435 - DBWS does not handle %ROWTYPE mix of PL/SQL types and JDBC Advanced types | *** 329435 - DBWS does not handle %ROWTYPE mix of PL/SQL types and JDBC Advanced types | ||
Revision as of 10:29, 9 November 2011
Dial In Info:
- please contact Peter Krogh for dial in information.
The EclipseLink committers have a regular meeting (currently weekly) to discuss ongoing development issues and projects. All interested parties are welcome to attend. If you have any additional items you wished discussed please add them at the bottom of the agenda including a brief description and any relevant links. Alternatively development issues can be discussed on the EclipseLink Dev mailing list.
* When adding agenda items please send an email to the eclipselink-dev@eclipse.org list notifying attendees. This will ensure attendees are aware of agenda items prior to the meeting.
Call Schedule
The calendar is available in the following formats:
iCal,
ATOM News Feed,
HTML
Agenda Oct 13, 2011
Ad Hoc
Release Planning
- 2.3.1 - GA Early November
- RC1 - Oct 17 (Complete)
- 2.4.0 - GA early Mar
- M5 - Oct 26 (In progress)
- M6 - Nov 9
- M7 - Nov 23
- M8 - Dec 7
- Indigo SR2 - GA Feb 24, 2012
- RC1+0 - Jan 16
- RC2+0 - Jan 30
- RC3+0 - Feb 8
- RC4+0 - Feb 13
- Juno - GA Jun 2012
- M1+1 - Missed
- M2+1 - Sept 26 (2.4.0-M3) (Complete)
- M3+1 - Nov 7 (2.4.0 M5?)
Migration to Git
- Kick off meeting to be scheduled
- Git demo?
- after we branch for 2.4
QA
October 27 - Nov 3, 2011:
- EclipseLink Nightly Results (Updated on 2011-11-03)
- trunk - 1 new failure with jaxb, seems to be related to the change with xmlparserv2.jar - investigating; server-test-composite failed on all WLS servers (10.3.5 with and without patch) - investigating; 15 new failures with jpa-server-test on WAS - test scripts issue, fixed by QA; DBWS examples failed on Glassfish (both v3.1.2 and 3.1.1) - investigating. (the last results is 2011-11-03)
- 2.3.1 - several new failures with jpa on WAS (all versions of WAS) - investigating; SDO server-testing failed on WAS 8 (both AS and ND) - server configuration issue, passed on WAS 7, low priority. On hold. (the last build is 2011-11-01)
- 2.2.2 - no new build (the last build is 2011-08-03)
- 2.1.4 - no new build (the last build is 2011-09-27)
- 2.0.3 - no new build (the last build is 2010-11-25)
- 1.2.1 - some failures with jpa testing on both JavaSE and JaveEE, they are all related to the environment setting, e.g. $JAVA_HOME or $JROCKIT_HOME. QA need to update the testing environment setting if there is a new release or new check it with this branch. (the last build is 2011-09-30)
- Testing
- trunk - JAXB errors... investigating
- trunk - The DBWS examples failed on all application servers - Investigating
- jpa/advancedproperties failure on WebSphere after we switch to 11.2.0.3 jdbc driver - fixed the issue (needed orai18n-mappings.jar) but this caused another issue in other tests (jpa/customfeature)
- Investigate and help developers debug sdo server test issue on WebSphere 8 as described in bug 362350
- 2.3.1 closedown - complete; additional testing -- ipV6 on Windows
- Doc review
- Test Dev
- JAX-RS integration with EclipseLink JAXB - 98%
- testGet() operations working.. need to implement and test remaining CRUD operations - ETA: Nov 5
- JAX-WS test project scoping -- initiated conversations with Dev
- JAX-RS integration with EclipseLink JAXB - 98%
- Test infrastructure
- Investigated weekly performance testing issue - fixed (out of HD space) - had to archive old results
- Nightly automation switched to Oracle DB 11.2.0.3 - made changes to accomodate new xdb6.jar which is needed by our Oracle customfeature tests
- This week:
- JAX-RS integration with EclipseLink JAXB
- JAX-WS test project
- solution for jpa/customfeature model on websphere
- Resolve issues with SDO / WAS 8
- (backlog) Change EclipseLink Nightly Testing scripts for Tycho adoption in trunk - continue to monitor what else needs to be done
- (backlog) Add "is.JPA1.0" flag in WDF server testing framework in order to skip those JPA2.0 tests on only JPA1.0 supported application servers.
Build
October 27, 2011:
- Milestone Releases
- 2.4.0 M5 (Oct 27 - 2.4.0.v20111026-r10274) (in Progress)
- Next: Nov 9 (2.4.0 M6?)
- API scanner - need to review (hold til Doug returns)
- add Hermes test bundle to build/ship? - need to review
- Tycho (New Build)
- Completed.
- Git
- Issues page started at: http://wiki.eclipse.org/EclipseLink/Build/Git
- Updates ongoing
- Troubleshooting Maven uploads
JPA
- 2.4
- Schema provisioning
- MT - enhancements
- MT - Table per tenant
DBWS
2.4
- Feature: Parse DDL to extract database metadata
- This is a change in the way we access type metadata, that will cover off the following enhancement requests
- Sprints 6&7: Advanced Oracle types, PL/SQL types using %ROWTYPE% and %TYPE% macros, completed
- 325124, 339721 Provide support for strongly typed package REF CURSOR
- 339909 - DBWS should support optional argument queries
- 329435 - DBWS does not handle %ROWTYPE mix of PL/SQL types and JDBC Advanced types
- Folded runtime, builder code back into SVN
- Tests currently disabled while we get them running against new code
- This is a change in the way we access type metadata, that will cover off the following enhancement requests
- DBWS support for REST
- Ability to generate dynamic JPA persistence unit
- eclipselink-orm.xml describing the virtual entities and any named queries
- eclipselink-oxm.xml describing the mapping of the same entities to XML (and JSON)
- Ability to generate dynamic JPA persistence unit
MOXy / SDO
2.3.2
- Bug fixing - some MOXy performance issues highlighted
2.4
- Object model mapping to JSON
- MOXy footprint reduction
- Investigating how MOXy's dependency on foundation can be simplified to reduce binary/jar footprint
- Feature extensions
- Set of JAXB feature extensions targetted for 2.4 capture on roadmap (link above)
- Server integration testing
- JAX-RS testing: Working with QA to set up JAX-RS tests running in WLS & GlassFish
EclipseLink Incubator
EclipseLink/Development/Incubation
- Time to create separate sub-project for incubator
- Increase community of committers
- Try out GIT & eGit/jGit tooling in incubator?
Documentation
Preparing for 2.4 items. Ben put the EL doc plan on the wiki at http://wiki.eclipse.org/EclipseLink/Development/Documentation/2.4
Considering process improvements
JPA Doc: http://wiki.eclipse.org/EclipseLink/UserGuide/JPA
MOXy/JAXB Doc: http://wiki.eclipse.org/EclipseLink/UserGuide/MOXy
DBWS Doc: http://wiki.eclipse.org/EclipseLink/UserGuide/DBWS