-
Oct 9th, 2008, 08:41 AM
#1
Spring DM Server & EclipseLink
All,
I'm having trouble with getting eclipselink and spring server dm working.
Caused by: java.lang.NoClassDefFoundError: org/eclipse/persistence/jpa/PersistenceProvider
at org.springframework.orm.jpa.vendor.EclipseLinkJpaV endorAdapter.<init>(EclipseLinkJpaVendorAdapter.ja va:51)
1- I deployed the osgi eclipselink 1.1 version in
springsource-dm-server-1.0.0.RELEASE\repository\bundles\usr
10/08/2008 11:16 AM 58,159 org.eclipse.persistence.antlr-1.1-M2.jar
10/08/2008 11:16 AM 214,737 org.eclipse.persistence.asm-1.1-M2.jar
10/08/2008 11:16 AM 3,413,391 org.eclipse.persistence.core-1.1-M2.jar
10/08/2008 11:16 AM 443,100 org.eclipse.persistence.jpa-1.1-M2.jar
2- The jpa persistence jpa has the following export: (Which includes the org.eclipse.persistence.jpa)
Export-Package: org.eclipse.persistence.internal.jpa,org.eclipse.p ersi
stence.internal.jpa.deployment,org.eclipse.persist ence.internal.jpa.d
eployment.osgi,org.eclipse.persistence.internal.jp a.deployment.xml.pa
rser,org.eclipse.persistence.internal.jpa.jdbc,org .eclipse.persistenc
e.internal.jpa.metadata,org.eclipse.persistence.in ternal.jpa.metadata
.accessors,org.eclipse.persistence.internal.jpa.me tadata.accessors.cl
asses,org.eclipse.persistence.internal.jpa.metadat a.accessors.mapping
s,org.eclipse.persistence.internal.jpa.metadata.ac cessors.objects,org
.eclipse.persistence.internal.jpa.metadata.cache,o rg.eclipse.persiste
nce.internal.jpa.metadata.changetracking,org.eclip se.persistence.inte
rnal.jpa.metadata.columns,org.eclipse.persistence. internal.jpa.metada
ta.converters,org.eclipse.persistence.internal.jpa .metadata.copypolic
y,org.eclipse.persistence.internal.jpa.metadata.in heritance,org.eclip
se.persistence.internal.jpa.metadata.listeners,org .eclipse.persistenc
e.internal.jpa.metadata.locking,org.eclipse.persis tence.internal.jpa.
metadata.queries,org.eclipse.persistence.internal. jpa.metadata.sequen
cing,org.eclipse.persistence.internal.jpa.metadata .tables,org.eclipse
.persistence.internal.jpa.metadata.transformers,or g.eclipse.persisten
ce.internal.jpa.metadata.xml,org.eclipse.persisten ce.internal.jpa.tra
nsaction,org.eclipse.persistence.jpa,org.eclipse.p ersistence.jpa.osgi
,org.eclipse.persistence.tools.weaving.jpa
3- My own bundle creates the EclipseLinkVendorAdapter bean and import-package org.eclipse.persistence.jpa
My questions are:
What & Why is it not seeing the org.eclipse.persistence.jpa classes? [I am guessing the spring bundles aren't seeing the eclipselink osgi bundles] So I tried moving the eclipselink bundles to
springsource-dm-server-1.0.0.RELEASE\repository\bundles\ext
and the problem persists...
Any ideas? Is this because spring framework doesn't import the eclipselink bundle? Any ways around this? I will dig into the samples one of which seems to do exactly what I'm doing. I don't quite understand.
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules