Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EclipseLink » lazy instantiation of collections and the cache(how does the cache impact lazy updates to collections)
lazy instantiation of collections and the cache [message #1843029] Mon, 12 July 2021 14:36
joel sherriff is currently offline joel sherriffFriend
Messages: 1
Registered: July 2021
Junior Member
Hello, hope someone can shine a light on this...

Using eclipselink 2.6 with static weaving enabled and changetracking=true.

The problem is when doing an add to a large collection on an entity. The first time (when the entity is not found in the cache), it works great...the collection is not instantiated. The second and subsequent times though, the entire collection is instantiated.

The entity is annotated with @ChangeTracking(ATTRIBUTE).

Lazy instantiation of the collection seems to be defeated when it's found in the cache due to shouldAllowInstantiationDeferral() returning false in IndirectList because the WeavedAttributeValueHolderInterface is a simple ValueHolder and not a QueryBasedValueHolder like it is the first time.

I've yet to trace the difference back to something that we're doing in the application. Is there something I'm missing? Thanks.
Previous Topic:JPA INSERT caused Oracle Version_Count increase High
Next Topic:SDO deprecation
Goto Forum:
  


Current Time: Fri Dec 02 09:57:21 GMT 2022

Powered by FUDForum. Page generated in 0.02105 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top