org.eclipse.persistence.jpa.PersistenceProvider not found

[ebross]

IDE: Eclipse
OS: jboss-as-7.0.2.Final
Platform: Linux
Project: EAR (also deployed as ear)
JPA: None --Using Neo4j graph db

I am not using JPA, hence no persistence.xml, nor is there any use of exclipselink api in my code. And yet I keep having  a "org.eclipse.persistence.jpa.PersistenceProvider  not found" error.  If there should be any such error, it should be on hibernate -- the default provider used in JBoss.

I have done some search, but it would seem that the errors are related to jpa and persistence.xml, but  I am not  using any of those stuff and should not be having this error. Cyber fiends, any clue(s)?

Thanks

Stack trace

13:04:53,711 INFO  [org.jboss.weld] (MSC service thread 1-1) Starting Services for CDI deployment: osasEAR.ear
13:04:53,725 INFO  [org.jboss.weld] (MSC service thread 1-5) Starting weld service
13:04:55,870 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.subunit."osasEAR.ear"."osasWeb.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."osasEAR.ear"."osasWeb.war".INSTALL: Failed to process phase INSTALL of subdeployment "osasWeb.war" of deployment "osasEAR.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.0.2.Final.jar:7.0.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.7.0_01]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.7.0_01]
at java.lang.Thread.run(Thread.java:722) [:1.7.0_01]
Caused by: javax.persistence.PersistenceException: PersistenceProvider '
org.eclipse.persistence.jpa.PersistenceProvider  ' not found
at org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.lookupProvider(PersistenceUnitDeploymentProcessor.java:491)
at org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.addPuService(PersistenceUnitDeploymentProcessor.java:245)
at org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.handleWarDeployment(PersistenceUnitDeploymentProcessor.java:170)
at org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.deploy(PersistenceUnitDeploymentProcessor.java:100)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.0.2.Final.jar:7.0.2.Final]
...

[smarlow]

Can you show a list of files in osasWeb.war?

[ebross]

Thanks, but you have to be more specific (e.g. classes, jar etc): osasWeb contains over 500 files of various extensions. There are, however, no jsf, jsp, or html files -- I am using vaadin and gwt.

[smarlow]

From a command shell, if you just do a "jar tf osasWeb.war > output.txt" and paste the contents of output.txt on pastie.org (post the link here), that is fine or attach it here (see option to attach files after clicking "use advanced editor").

The error that you are getting, is what I would expect to see if you had a persistence.xml that referenced the EclipseLink persistence provider.  I would like to see the archive contents so we can figure out, why that might be happening. 

Usually, the as7/standalone/log/server.log (and AS7 console) would show the message "JBAS011401: Read persistence.xml for NAME", if an actual persistence.xml is found in the application, so I'm not yet sure of the issue.  Showing the files contained in the application, should give us an idea.

It might also help to attach the contents of your server.log.

[ebross]

Thanks Scott "jar tf osasWeb.war produced 2,578 files. Can't paste them due to legal reasons. Anyway, I found the problem and it is to do with one of the vaadin addons I and using in the project. It demands eclipselink without stating so in its documentation. I have removed the addon, and doing fine without it.

Thanks