You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Martin Wiesner (Jira)" <ji...@apache.org> on 2020/11/27 13:34:00 UTC
[jira] [Updated] (TOMEE-2931) [Certification/TCK] JPA EE packaging
failing for EAR files
[ https://issues.apache.org/jira/browse/TOMEE-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Wiesner updated TOMEE-2931:
----------------------------------
Affects Version/s: 8.0.5
> [Certification/TCK] JPA EE packaging failing for EAR files
> ----------------------------------------------------------
>
> Key: TOMEE-2931
> URL: https://issues.apache.org/jira/browse/TOMEE-2931
> Project: TomEE
> Issue Type: Bug
> Affects Versions: 8.0.5
> Reporter: Jean-Louis Monteiro
> Priority: Major
> Attachments: image-2020-11-27-11-13-13-896.png
>
>
> The test is com.sun.ts.tests.jpa.ee.packaging.jar.Client --> [https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/src/com/sun/ts/tests/jpa/ee/packaging/jar/Client.java]
>
> This error is this one
> {quote}Caused by: Exception [EclipseLink-28018] (Eclipse Persistence Services - 2.7.4.v20190115-ad5b7c6b2a): org.eclipse.persistence.exceptions.EntityManagerSetupException
> Exception Description: Predeployment of PersistenceUnit [CTS-EM] failed.
> Internal Exception: java.lang.RuntimeException: java.io.FileNotFoundException: /Users/<path>/jakartaeetck-prebuilt-8.0.2/release/jakartaeetck-prebuilt-8.0.2/dist/com/sun/ts/tests/jpa/ee/packaging/jar/jpa_ee_packaging_jar_vehicles/lib/jpa_ee_packaging_jar_jarfile1.jar (No such file or directory)
> at org.eclipse.persistence.exceptions.EntityManagerSetupException.predeployFailed(EntityManagerSetupException.java:233)
> ... 63 more
> Caused by: java.lang.RuntimeException: java.io.FileNotFoundException: /Users/<path>/jakartaeetck-prebuilt-8.0.2/release/jakartaeetck-prebuilt-8.0.2/dist/com/sun/ts/tests/jpa/ee/packaging/jar/jpa_ee_packaging_jar_vehicles/lib/jpa_ee_packaging_jar_jarfile1.jar (No such file or directory)
> at org.eclipse.persistence.internal.jpa.metadata.MetadataProcessor.loadStandardMappingFiles(MetadataProcessor.java:491)
> at org.eclipse.persistence.internal.jpa.metadata.MetadataProcessor.loadMappingFiles(MetadataProcessor.java:400)
> at org.eclipse.persistence.internal.jpa.deployment.PersistenceUnitProcessor.processORMetadata(PersistenceUnitProcessor.java:619)
> at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.predeploy(EntityManagerSetupImpl.java:2003){quote}
>
> If we open the EAR file and look at the persistence.xml it indeed has 2 jar-file entries. Great.
> !image-2020-11-27-11-13-13-896.png!
> But if we look at the file name and compare it to what's on the left side (EAR content), we can see that the jar file name is not fully the expected one.
>
> Before 1 and 2, there is a "jarfile" in the persistence.xml
>
> I don't see how it could work.
> What do you think?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)