Toplink JPA LAZY loading in Java SE works without javaagent?

Question

hi there,
I tought that mappings like
@JoinColumn(name = "join_col_name")
@ManyToOne(cascade=CascadeType.ALL, fetch=FetchType.LAZY)
private RelatedObject relObj;
with TopLink JPA in Java SE environment works ONLY with the
-javaagent:toplink-essentials-agent.jar
JVM parameter?
the strange thing is: I did 2 test runs, with and without the java agent parameter. I also could see that in the first case the weaver is working, in the second the property "toplink.weaving=false" is printed to the console BUT if I access the LAZY mapped attribute of the object instance it works in both cases - I expected a NullPointerEx. in the case without the javaagent.
Is there anything I missed?
Hans

Answer 1

Chris,
thank for for the tip about verifying lazy or eager fetching. The results are interesting - or better: confusing - to me:
I have built a test project with 3 entities:
Entity A hast @OneToMany to Entity B and
Entity B has ManyToONe to Entity C
A <-- B --> C
ALL relations are marked with FetchType.LAZY in all directions.
When I simply run the test project via main()-method out of eclipse, WITHTOUT specifycing a -javaagent parameter in the run dialog, I can confirm using your test case that the realtion IS LAZILY FETCHED.
So, I do not really know how this should work without the javaagent.
You mentioned statically weaved classed - is this the default case when no agent is present, how is it done? Toplink logging says that weaving is NOT active:
ServerSession(16821027)--Thread(Thread[main,5,main])--property=toplink.weaving; value=false
so how can the lazy loading work then?
regards,
Hans