[
https://issues.jboss.org/browse/WFLY-459?page=com.atlassian.jira.plugin.s...
]
Jason Greene commented on WFLY-459:
-----------------------------------
:( If we do this we would be adding yet another breakage from the ideal of modular class
loading. The only thing a modular class loader should see is APIs. It should never see
implementation dependencies. Most of the time this happens, its because the framework is
using the wrong class loader (e.g TCCL to load its own classes vs the defining class
loader). We have some historic baggage here but we should not be adding new cases of it
javassist should also be exported to Hibernate (native) applications
--------------------------------------------------------------------
Key: WFLY-459
URL:
https://issues.jboss.org/browse/WFLY-459
Project: WildFly
Issue Type: Task
Components: JPA / Hibernate
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 10.0.0.CR5
Originally this jira was to stop exporting the javassist module to JPA deployments but it
turns out that is fine to do. In addition, native Hibernate applications that depend on
Hibernate, should also get the javassist dependency.
# native Hibernate applications will get the javassist dependency via the application
dependency on org.hibernate.
# container managed JPA applications will get the javassist dependency via
org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer).
# container managed JPA applications that embed their own copy of Hibernate jars will
also get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor
(JPA deployer).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)