[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipselink-users] Weaving question
|
Hi Rafal,
The way LAZY loading works in EclipseLink for Basic mappings is a bit
different from the way it works for xToOne mappings.
With xToOne mappings, for each mapping, a structure is weaved in to deal with
that mapping and they are dealt with individually.
With Basic mappings, we user our Fetch group support. LAZY Basic mappings
are excluded from the default fetch group and so the initial query for an object
with LAZY basic mappings will not get the objects those mappings refer to. Any
reference to a LAZY basic mapping that causes it to be retrieved will cause the
whole object to be loaded.
The JPA spec defines LAZY as a hint (i.e. there is no mandatory behavior),
and that is the way we have chosen to implement that hint for LAZY Basics. If
you think this is a major limitation, please feel free to enter an enhancement
request.
You should be able to use Fetch groups to configure which parts of the object
are loaded more finely. Here is some info:
http://wiki.eclipse.org/Configuring_a_Descriptor_%28ELUG%29#Configuring_Fetch_Groups
As far as the weaved classes are concerned, we use ASM for byte code weaving.
The debugging behavior you see is the default behavior when using that tool.
-Tom
Swierzynski, Rafal wrote:
Hi EL users and devs,
after seeing some email on weaving in SE, I decided to try this myself. I configured it and it works. However, I noticed something strange.
My @Entity class is very simple: Id (Long), Name (String, eager), Huge (String, lazy). Now when I invoke EntityManager.find() the first SQL is:
SELECT ID, NAME FROM PERSON WHERE (ID = ?)
which proves that Huge is lazy loaded. Now, I get this via a getter, and the SQL generated is this:
SELECT ID, HUGE, NAME FROM PERSON WHERE (ID = ?)
As you can see, the same data (Id and Name in this case) is selected twice from the database. In my case it is very little data, but I can imagine a scenario when a lot of data gets selected twice. Maybe I am missing some configuration property?
Then, I added another LAZY field, huge2. They don't get selected at first, as planned, but when I reference any of the lazy fields, both are selected.
Are these 2 use cases supposed to work this way, or should I configure something additionally?
As a side question: to satisfy my curiosity, I output and decompiled the weaved class, and the source is much different. However, I could debug through the entity, and it worked fine, the breakpoints were put in the appropriate lines and the debugger worked perfectly, it was totally invisible that the class's bytecode was changed and didn't correspond to the (original) source. How did you do this? What magic did you use for that? Do you mess with the internal class file's sumbol tables somehow to map the new bytecode to the old source or something?
Regards,
Rafał
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
