|Wildfly 10.0.0.Final - Sample War App - Using Eclipselink 2.6.4 - jar-file paths not properly handle [message #1754674]
||Tue, 21 February 2017 13:02
| Nuno Godinho de Matos
Registered: September 2012
I am opening this issue in the eclipselink forum.
I believe eclipselink is the most likely owner for this bug - not wildfly.
The issue being reported here is also open for comment in:
When using wildfly 10, it is impossible to make the <jar-file> elements of a persistence.xml work properly.
A developer is forced to use the declaration of every single class in the persistence.xml to make a deployment go through.
- this is actually no work-around, as such "maintenance hell" literally means one is forced to use Hibernate, because class over jar-file is no alternative at all.
The jar-file scanning is, in my opinion, an absolutely critical API offered by the persistence.xml. This functionality should work flawlessly in every container - including wildfly.
Be able to deploy a war file that refers to entities inside web-inf/lib should work in every container where eclipselink can be chosen as the JPA layer provider. This is not the case for wildfly.
A sample application is given that can be used to test a deployment both with Hirbernate and Eclipselink against wildfly 10, only hibernate seems at this point in time to be prepared to adequately handle the jar-file values in the wildfly echosystem, that creates :vfs URLs to the resources.
Please visit the following URL:
It should be possible to have the jar-file declarions work both when deployment from eclipse as well as deploying the pure war file to Wildfly 10.
The lack of such a feature is essentially forcing a person in wildfly to have to choose to use hibernate over eclipselink, which is something I would sincerely prefer to avoid.
Would it be possible to get a comment on this?
And if this issue is recognized as a bug, would it be possible to get an eclipselink 2.6.4/5/6/ patch release that addresses this problem.
[Updated on: Tue, 21 February 2017 13:07]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.02089 seconds