[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipselink-dev] Unexpected AssertError
|
Hello John,
There is a pre-existing bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=210280 which was fixed for
jars but based on your report seems to be still broken for files.
Could you please reopen the bug and post your new findings.
Thank you,
--Gordon
vrmerlin wrote:
We're evaluating EclipseLink as a potential JPA solution. When running M9 in
an Eclipse project, I was getting the following error:
Exception in thread "main" java.lang.AssertionError
at
org.eclipse.persistence.internal.jpa.deployment.PersistenceUnitProcessor.computePURootURL(PersistenceUnitProcessor.java:137)
at
org.eclipse.persistence.jpa.PersistenceProvider.createEntityManagerFactory(PersistenceProvider.java:98)
at
org.eclipse.persistence.jpa.PersistenceProvider.createEntityManagerFactory(PersistenceProvider.java:64)
at
javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:83)
at
iccs.base.db.jdbcpool.ConCacheGetter.getEntityManager(ConCacheGetter.java:233)
at
iccs.services.system_manager.server.ProcessDataModel.<init>(ProcessDataModel.java:49)
at
iccs.services.system_manager.server.SysMgrCentralImpl.<init>(SysMgrCentralImpl.java:76)
at
iccs.services.system_manager.server.SysMgrServerMain.<init>(SysMgrServerMain.java:52)
at
iccs.services.system_manager.server.SysMgrServerMain.main(SysMgrServerMain.java:71)
Looking down into the eclipselink source code, it appeared that EclipseLink
was failing the isFile() test for the persistence.xml file it found. The
reason it failed was because there was a space in the path to that file (in
particular, my eclipse project name). When I created a new project (without
a space), the problem went away and things went fine.
It took quite some time to track down why I was getting this rather
ambigious error, and I don't think I should have gotten it in the first
place (OpenJPA and Hibernate didn't have any problems with my Eclipse
project name at all). I'd really rather not put that artificial constraint
on our developers.
Having a space in the path to the persistence.xml file seems reasonable...
however, I can't find much mention of anyone else having this problem. Any
thoughts on how I might fix it?
btw, I'm using JDK 6u10.
Thanks,
John
