Eclipse Community Forums: EclipseLink » Wildfly 10.0.0.Final - Sample War App - Using Eclipselink 2.6.4

Home » Eclipse Projects » EclipseLink » Wildfly 10.0.0.Final - Sample War App - Using Eclipselink 2.6.4 - jar-file paths not properly handle(Eclipselink integration with wildfly not handling properly persistnece.xml jar-file)

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 08:02

Eclipse User

Hi,

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:
- https://developer.jboss.org/message/968943#968943
- http://stackoverflow.com/questions/42354357/wildfly-10-0-0-final-persistence-xml-jar-file-element-not-properly-supported-w

PROBLEM:
When using wildfly 10, it is impossible to make the <jar-file> elements of a persistence.xml work properly.

WORK-AROUND:
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.

ADDITIONAL COMMENTS:
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.

SAMPLE APPLICATION:
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:
https://github.com/99sono/eclipselink-wildfly-jar-file-issue

NOTE:
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.

Kind regards.

[Updated on: Tue, 21 February 2017 08:07] by Moderator

Re: Wildfly 10.0.0.Final - Sample War App - Using Eclipselink 2.6.4 - jar-file paths not properly ha [message #1754858 is a reply to message #1754674]

Thu, 23 February 2017 04:25

Eclipse User

Hi,

The issue is addressed.
In fact jboss implements support for the virtual file system.
They provide their own implementation of an eclipselink archive factory that knows how to scan this URLs.

The answer for the problem is given both the stack overflow and jboss threads.

Kind regards.

Re: Wildfly 10.0.0.Final - Sample War App - Using Eclipselink 2.6.4 - jar-file paths not properly ha [message #1754859 is a reply to message #1754674]

Thu, 23 February 2017 04:25

Eclipse User

Previous Topic:	Does it possible to make "alter online table" queries in mysql/mariadb
Next Topic:	eclipselink History Policy: custom field

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 22:34:08 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter