re of enhancement or the generated code is
invalid.
Again, this has nothing to do with lazy loading or dirty tracking.
Regards,
Luis Barreiro
Middleware Performance Team
<https://red.ht/sig>
On 9/9/19 10:55 PM, Gail Badner wrote:
> Hi Luis,
>
> IIUC, HHH-13446 deals with a m
ceeds but the resulting classes are
invalid.
Regards,
Luis Barreiro
Middleware Performance Team
<https://red.ht/sig>
On 9/5/19 10:54 PM, Gail Badner wrote:
> HHH-13317 is specifically a bug with bytecode enhancement using Javassist.
>
> It showed up when running a test added for
to release Agroal 1.4 that will include this
fix.
Regards,
Luis Barreiro
Middleware Performance Team
<https://red.ht/sig>
On 1/30/19 2:43 PM, Steve Ebersole wrote:
> I hate to be overly reactionary, but we we may want to consider
> dropping that module then. If there is a bu
perty access.
I think we need to sort out both aspects, the interception and enhancing
as mapped collection, in order to support this case properly. The former
is a bug but for the latter I don't see a good enough solution.
Let me know what you find so we can proceed on solving this out.
Rega
at a time), hence my question about synchronization, but you
were obviously looking at a different level.
Regards,
Luis Barreiro
Middleware Performance Team
<https://red.ht/sig>
On 06/05/2018 07:08 PM, Scott Marlow wrote:
> Thanks, I think they probably intended that the persis
class loader)
Also, in theory, you could have multiple transformations applied to the
same entity / PU. So what is it you really want to check ?!
I don't get you last paragraph ... why ORM will be only capable of
registering one transformer, and why will you need synchronization ?!
Rega
te is not something you can
enable or disable.
The only thing configurable is the bytecode provider, and that is
something that has indeed changed for 5.3. AFAICT the generated bytecode
should be identical.
Luis Barreiro
Middleware Performance Team
<https://red.ht/sig>
On 05/18/20
ot aware of any plans to change the current behavior.
Regards,
Luis Barreiro
Middleware Performance Team
<https://red.ht/sig>
On 01/18/2018 09:39 PM, Scott Marlow wrote:
> Hi,
>
> Did we change Hibernate to automatically enhance/rewrite application
> entity classes by default
ibernate/hibernate-orm/blob/master/documentation/src/main/docbook/userGuide/en-US/chapters/enhancement/BytecodeEnhancement.xml
>
>
> Ah, because it's not in 5.0 :) That's in master for 5.1
>
--
Luis Barreiro
JBoss^® by Red Hat
___
possible issue.
To help current users unaware of this change, a warn should be
printed if a plugin runs without any feature enabled.
Finally, as part of issue HHH-10354 I propose renaming the
undocumented feature 'enableFieldAccessEnhancement' to
'enableExtendedEnhance
a (org.hibernate.mapping) at all; it parses the entity annotations
>> (completely annotation specific) on its own. Given the 2-phase break down
>> in JPA bootstrapping, having Enhancer leverage the built metadata is not
>> really going to be possible. Which is unfortunate, becau
t;> [4]
>>> https://github.com/wildfly/wildfly/blob/master/testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/jpa/hibernate/classfiletransformertest/ClassFileTransformerTestCase.java
>>> ___
>>> hibernate-dev mailing list
&g
12 matches
Mail list logo
