[
https://issues.redhat.com/browse/WFLY-13714?page=com.atlassian.jira.plugi...
]
Scott Marlow commented on WFLY-13714:
-------------------------------------
{quote}
The vfs url should be resolved to a plain file or jar URL that actually exists on file
system before passing the URL to a JPA provider when creating an EntityManagerFactory.
{quote}
[~java202020] sorry for the delay in responding. It has been around 10 years or so since
I tried insulating the JPA providers from VFS but it wasn't a 1-1 mapping for all
deployments.
Are you trying to use a custom persistence provider?
JPA PersistenceUnitInfo.persistenceUnitRootUrl vfs URL should be
resolved
-------------------------------------------------------------------------
Key: WFLY-13714
URL:
https://issues.redhat.com/browse/WFLY-13714
Project: WildFly
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 20.0.1.Final
Reporter: Java Java
Assignee: Scott Marlow
Priority: Major
Wildlfy passes a PersistenceUnitInfo object to JPA provider using vfs URL as
persistenceUnitRootUrl, e.g.,
vfs:/C:/wildfly-20.0.1.Final/bin/content/foo.ear/myejb.jar/
A JPA provider can not resolve this URL without using a third-party library and thus
force
the JPA provider to have dependency on 3rd party libraries or wildfly.
The vfs url should be resolved to a plain file or jar URL that actually exists on file
system before passing the URL to a JPA provider when creating an EntityManagerFactory.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)