Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334883 - Gemini JPA 1.0.0 M3 is broken against EclipseLink 2.2.0 RC3
Summary: Gemini JPA 1.0.0 M3 is broken against EclipseLink 2.2.0 RC3
Status: RESOLVED FIXED
Alias: None
Product: Gemini.JPA
Classification: RT
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 critical (vote)
Target Milestone: 1.0.0 M4   Edit
Assignee: Michael Keith CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-20 08:59 EST by David Schmitz CLA
Modified: 2011-02-14 11:12 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Schmitz CLA 2011-01-20 08:59:11 EST 
Build Identifier: Gemini JPA 1.0.0 M3

Eclipse Gemini 1.0.0 M3 does not work against EclipseLink 2.2.0 RC3 because Gemini JPA references the class org.eclipse.persistence.internal.jpa.deployment.PersistenceInitializationHelper of EclipseLink which was deleted since SVN revision 8730. 
This means that all release candidates of EclipseLink 2.2.0 do not work against Gemini JPA. 

The following classes within Gemini JPA reference the missing class:
- org.eclipse.gemini.jpa.provider.GeminiOSGiInitializer
- org.eclipse.gemini.jpa.provider.PersistenceProvider

Reproducible: Always

Steps to Reproduce:
1. Use latest EclipseLink 2.2.0 RC3
2. Start your application and it will crash with ClassNotFoundException for Class 
org.eclipse.persistence.internal.jpa.deployment.PersistenceInitializationHelper
Comment 1 Shaun Smith CLA 2011-01-24 14:13:36 EST 
Resolve by Bug 332743.