Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "EclipseLink/Development/Backlog"

Line 8: Line 8:
 
! Bug/ER #
 
! Bug/ER #
 
! Description  
 
! Description  
|-
 
| || Support for usage of Oracle TopLink's 10.1.3 and 11gR1 XML metadata (sessions.xml and deployment map XML). This will enable existing customers to more easily try out EclipseLink.
 
|-
 
| || Migration utility for migrating source and configuration from TopLink Essentials JPA to EclipseLink JPA
 
|-
 
| || How-To migrate from TopLink Essentials to EclipseLink
 
|-
 
| || Migration utility for migrating source and configuration from Oracle TopLink (native ORM) to EclipseLink's native ORM
 
 
|-
 
|-
 
| || How-To migrate from Oracle TopLink's native ORM support to EclipseLink
 
| || How-To migrate from Oracle TopLink's native ORM support to EclipseLink
Line 45: Line 37:
 
| || How-To use EclipseLink JPA within Spring
 
| || How-To use EclipseLink JPA within Spring
 
|  
 
|  
 +
|}
 +
 +
Completed
 +
{|{{BMTableStyle}}
 +
|+{{BMTableCaptionStyle}}|Bugs Committed
 +
|-{{BMTHStyle}}
 +
! Bug/ER #
 +
! Description
 +
|-
 +
| || DONE - Support for usage of Oracle TopLink's 10.1.3 and 11gR1 XML metadata (sessions.xml and deployment map XML). This will enable existing customers to more easily try out EclipseLink.
 +
|-
 +
| || DONE - Migration utility for migrating source and configuration from TopLink Essentials JPA to EclipseLink JPA
 +
|-
 +
| || DONE - How-To migrate from TopLink Essentials to EclipseLink
 +
|-
 +
| || DONE - Migration utility for migrating source and configuration from Oracle TopLink (native ORM) to EclipseLink's native ORM
 +
|-
 +
| || DONE - How-To migrate from Oracle TopLink's native ORM support to EclipseLink
 +
|-
 
|}
 
|}

Revision as of 13:51, 2 November 2007

This page is a prioritized list of enhancements to be made to the EclipseLink project. The intent is that this list be used to plan future development cycles taking the top most items. While not all filed bugs and enhancement requests will be captured here the most important ones should be listed to have them addressed in an upcoming cycle.

Last revised: --2007-11-02

Bugs Committed
Bug/ER # Description
How-To migrate from Oracle TopLink's native ORM support to EclipseLink
200040 New native XML metadata format: Provide new metadata format that is more readable, uses configuration by exception, and aligns with JPA's ORM.XML for override or full replacement.
 ? Remove Deprecated Logging: Remove the deprecated logging classes from the o.e.p.sessions package (SessionLog, SessionLogEntry, DefaultSessionLog)
 ? Remove Deprecated SDK-XML mapping and associated legacy metadata read/write functionality
 ? Remove Deprecated SDK mappings. Some non-deprecated mappings (i.e. object-relational mappings) will require keeping some of the functionality.
 ? Remove Deprecated MBeans support in deprecated.services support.
 ? Dynamic Persistence: Make the dynamic persistence capability generally available and usable with JPA, SDO, DBWS, and MOXy. Enable full capabilities of a woven class in a dynamic entity. This effort will involve combining the existing SDO and DBWS solution into a single offering in a public package in the eclipselink.core project.
 ? Remove unused import statements reported by Eclipse IDE in eclipselink.core project. Approximately 138 warnings.
 ? Remove unused import statements reported by Eclipse IDE in eclipselink.extension.oracle project. Approximately 8 warnings.
 ? Remove unused import statements reported by Eclipse IDE in eclipselink.jpa project. Approximately 25 warnings.
 ? Remove unused local or private members reported by Eclipse IDE in eclipselink.core project. Approximately 32 warnings.
 ? Remove local variable never read warnings reported by Eclipse IDE in eclipselink.core project. Approximately 226 warnings.
Provide a Vendor adapter for using EclipseLink JPA within the Spring Framework. Need to decide if this is part of EclipseLink or should the adapter be contributed to Spring?
How-To use EclipseLink JPA within Spring

Completed

Bugs Committed
Bug/ER # Description
DONE - Support for usage of Oracle TopLink's 10.1.3 and 11gR1 XML metadata (sessions.xml and deployment map XML). This will enable existing customers to more easily try out EclipseLink.
DONE - Migration utility for migrating source and configuration from TopLink Essentials JPA to EclipseLink JPA
DONE - How-To migrate from TopLink Essentials to EclipseLink
DONE - Migration utility for migrating source and configuration from Oracle TopLink (native ORM) to EclipseLink's native ORM
DONE - How-To migrate from Oracle TopLink's native ORM support to EclipseLink

Back to the top