Hi Patrik Mihalcin,

Thanks for your report.

Unfortunately, I don't think we can do much for you. AFAICS you have several issues here:

• having 4 persistence providers deployed is definitely not a good idea. Don't you have a way in WebLogic to disable the ones you don't use? Frankly, even if you fix your issue, iterating over all the providers to check if each property of each entity is loaded will be slow.
• apparently, EclipseLink PersistenceProvider cannot be cast to the standard javax.persistence.spi.PersistenceProvider. Wondering if it's using the same JPA dependency the others are using.

In the end, I really think it's an issue with your WebLogic installation and you should try to disable the persistence providers you don't use.

If you don't have lazy properties or if you don't care about loading them when validating your entities, you can set up your own TraversableResolver always returning true. See https://docs.jboss.org/hibernate/stable/validator/reference/en-US/html_single/#section-validator-factory-traversable-resolver .

But I would definitely try to fix the WebLogic installation first.