EclipseLink project works in one Eclipse Workspace but not in anotherhttps://www.eclipse.org/forums/index.php/mv/msg/125632/385175/#msg_385175
I have a very small EclipseLink example which runs perfectly in a
workspace.

I imported this example in another workspace (same Eclipse installation
therefore same version, available plug-ins, etc.) and it did not work.

The following message was issued:

Exception in thread "main" javax.persistence.PersistenceException: No
Persistence provider for EntityManager named people
at
javax.persistence.Persistence.createEntityManagerFactory(Per sistence.java:89)
at
javax.persistence.Persistence.createEntityManagerFactory(Per sistence.java:60)
at de.vogella.jpa.eclipselink.main.Main.main(Main.java:18)

After lots of checking the only difference I could find is that the
second workspace is in a deep folder structure, something like:
C:\Documents and
Settings\vogella\Desktop\Documents\08_MyDocuments\20_Documen tation\JPAPersistenceExamples\de.vogella.jpa.eclipselink2\sr c\META-INF

I imported the project into a thrid workspace with a shorter path (again
same Eclipse installation) and it did work.

Are there any restrictions in relation to the path name or are there any
other reasons why the project does not run in the second workspace?

What version of EclipseLink are you using.
--Gordon]]>Gordon Yorke2009-01-12T01:00:08-00:00Re: EclipseLink project works in one Eclipse Workspace but not in anotherhttps://www.eclipse.org/forums/index.php/mv/msg/125632/385180/#msg_385180
For this example I'm using eclipselink-1.0.2.

I did try this example in a workspace which had also spaces (but a
shorter path name) and it worked.

The path in which the example is working: is
C:\Documents and
Settings\vogella\Desktop\Documents\08_MyDocuments\14_Eclipse _Test_Path\de.vogella.jpa.eclipselink

The none working path is:
C:\Documents and
Settings\vogella\Desktop\Documents\08_MyDocuments\20_Documen tation\JPAPersistenceExamples\de.vogella.jpa.eclipselink

Best regards, Lars

Gordon Yorke wrote:
> The failing project has spaces in the path. We have fixed a similar
> issue in 1.1 and I believe 1.0.2.
>
> What version of EclipseLink are you using.
> --Gordon
>

Running this in a project with a medium sized path name delivers a hit.
Running it in a project with a long path name return nothing.

I'll open a bug at Sun.

Best regards, Lars]]>Lars Vogel2009-01-12T20:44:55-00:00Re: EclipseLink project works in one Eclipse Workspace but not in anotherhttps://www.eclipse.org/forums/index.php/mv/msg/125632/385243/#msg_385243
Hi, just a reference about 1.6 releases to keep in mind.
The implementation of releases post 1.6.0_07 differ in their
ClassLoader behavior.
We had a classLoader issue in SDO recently where when we loaded >5000
classes the JVM slowed down by a factor of 300+. It turned out that this
behavior only appeared from 1.6.0_01 to 1.6.0_07, when we used a 1.5 JRE
or the 1.6.0_10 JRE there was no issue. It looked like the ClassLoader
implementation in the 1.6.0_10+ JRE's may use a different improved HotSpot
JVM.