Wildfly 11 and EclipseLink entity scanning

[alessandromoscatelli]

Hi everybody,

is somebody using EclipseLink as JPA Provider with Wildfly 11 without manually listing classes in persistence.xml ?

I didn't manage to accomplish such task, I tried everything (of course I started following the wildfly official documentation).

I suspect this is a problem related with the last version of jipijapa.

Am I the only one ?
Thank you in advance.

JPA Reference Guide - Latest WildFly Documentation  - Project Documentation Editor

[WFLY-9878] EclipseLink Entity Scanning broken in Wildfly 11 - JBoss Issue Tracker

[andey]

EclipseLink is not shipped with Wildfly also not compatible/tested components with Wildfly.. It is a 3rd party components which can be integrate with Wildfly.

The community documentation shows how to install EclipseLink as a module:

JPA Reference Guide - WildFly 10 - Project Documentation Editor

JPA Reference Guide - Latest WildFly Documentation - Project Documentation Editor

How to use EclipseLink with AS7

[smarlow]

Please list the contents of your ear and/or war/jar files (e.g. show output from "jar tf yourApp.jar"). If you don't want to list the entire contents, that is fine, I'm just curious as to where the persistence.xml file is and where the entity classes are as well, in your deployment. 

It is hard to guess as to where the bug is exactly.  I'm not sure if the EclipseLink (org.eclipse.persistence.internal.jpa.deployment.ArchiveFactoryImpl) logging would help or if debugging is needed.