[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[eclipselink-users] Weaving question
|
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ł
