[
https://issues.jboss.org/browse/WFLY-459?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on WFLY-459:
-----------------------------------
At the moment, our options are to leave org.jboss.as.jpa.processor.JPADependencyProcessor
as is (currently injects javassist into JPA deployments). Or, update the static Hibernate
ORM modules to export the javassist module dependency. The JPADependencyProcessor
approach is better as it covers deploying applications that include their own Hibernate
jars that might use javassist for enhancing entity classes (rewriting bytecode).
This issue is still open because its not really settled.
correct JPA dependency injection (stop injecting javassist)
-----------------------------------------------------------
Key: WFLY-459
URL:
https://issues.jboss.org/browse/WFLY-459
Project: WildFly
Issue Type: Task
Security Level: Public(Everyone can see)
Components: JPA / Hibernate
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 8.1.0.CR1
Rather than export the javassist dependency, see if we can change javassist to generate
proxies for the application classes which aren't on the hibernate module class path.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira