| Steve Ebersole I'm not sure, it might be helpful to see the WF testsuite pass with the pr. Some popular classloading configurations to consider:
- Application classloader accesses the Hibernate/Javassist classes via the system classloader (popular in non-modular environments, where the user just copies needed jars into a lib/jars folder).
- Application deployment is packaged with the Hibernate/Javassist classes, so application classloader already has the Hibernate/Javassist classes
- Application classloader has access to separate classloaders for Hibernate classloader and Javassist classloader (e.g. OSGi/WildFly).
- Application classloader has access to separate classloaders for Hibernate classloader and Javassist classloader (e.g. OSGi/WildFly) and application entity classes are also defined in a separate classloader. This is more rare but it comes up occasionally.
- Application classloader has access to separate classloaders for Hibernate classloader and Javassist classloader (e.g. Java 9 Jigsaw project).
|