[jboss-jira] [JBoss JIRA] (WFLY-8858) Remove JPA container check for deprecated hibernate.ejb.use_class_enhancer
[
https://issues.jboss.org/browse/WFLY-8858?page=com.atlassian.jira.plugin....
]
Scott Marlow commented on WFLY-8858:
------------------------------------
From
[http://lists.jboss.org/pipermail/hibernate-dev/2018-May/017693.html] conversation that
[~gbadner] started (thank you!).
Question from the discussion:
{quote}
In the past, I recall someone mentioning that lazy loading or dirty flag handling, would
depend on bytecode enhancing. If that happened or will happen, we should discuss what the
fallback solution is for when bytecode enhancing is not working.
{quote}
Response:
{quote}
Bytecode enhancement is not needed for either of these - Hibernate can (and has forever)
supported these without enhancement. That will continue to be the case. Bytecode
enhancement is simply an alternative means for adding these features.
However, certain features such as automatic bi-dir association management does require
enhancement to work.
{quote}
See above linked discussion for more details.
It seems to me that we don't need to fix anything in WildFly for [WFLY-8858], at least
not now. So, will close.
Remove JPA container check for deprecated
hibernate.ejb.use_class_enhancer
--------------------------------------------------------------------------
Key: WFLY-8858
URL: https://issues.jboss.org/browse/WFLY-8858
Project: WildFly
Issue Type: Task
Components: JPA / Hibernate
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 14.0.0.CR1
Applications can instead use the jboss.as.jpa.classtransformer property to control
whether the application can use entity class rewriting. Starting with Hibernate ORM 5.0+,
Hibernate defaults to always rewrite entity classes.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)