Unable to load persistence units from JPA persistence.xml if another persistence.xml with jta-data-source is there in classpath

Description

I've a application which is using JPA to perform database operations and has its own persistence.xml with unit-name as "myappunit".
This application is dependent on a 3rd party library that too has persistence.xml but with jta-data-source as it can be deployed within a container.
Now issue is, while trying to create an instance entity manager factory for unit-name "myappunit", I'm getting.

First of all, the above error message is very ambigious, as it is not telling for with persistence.xml the exception is thrown. One need to enable trace level logs of hibernate to figure out for which persistece.xml the exception is thrown.

Upon further debugging and enabling logs I found that in doResolve of PersistenceXmlParser, if validation of even one persistence.xml fails, the complete process of creation of entity manger gets beak.

I think the logic should continue with rest of persistence.xml's and the proper exception handling should be there along with logging.

The current code for doResolve in PersistenceXmlParser is

It would be nice if it will be modified as

Environment

Windows

Activity

Show:
Steve Ebersole
October 27, 2015, 7:14 PM

This bug report does not indicate that the reported issue affects version 5.x. Versions prior to 5.x are no longer maintained. It would be a great help to the Hibernate team and community for someone to verify that the reported issue still affects version 5.x. If so, please add the 5.x version that you verified with to the list of affected-versions and attach the (preferably SSCCE) test case you used to do the verification to the report; from there the issues will be looked at during our triage meetings.

For details, see http://in.relation.to/2015/10/27/great-jira-cleanup-2015/

Steve Ebersole
October 28, 2015, 3:25 AM

As part of verifying that this issue affects 5.0, please just set the "Affects version". Leave the "verify-affects-5.0" label and leave the issue in "Awaiting Response" status; these are critical for us to be able to track these verifications and triage them. Thanks.

Assignee

Unassigned

Reporter

Mayank Mittal

Fix versions

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Components

Affects versions

Priority

Major
Configure