Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Talk:EclipseLink/UserGuide/JPA/Basic JPA Development/Mapping/Basic Mappings/Lazy Basics"
m |
m |
||
Line 13: | Line 13: | ||
::When using a [[Introduction%20to%20EclipseLink%20JPA%20(ELUG)#@OneToOne|one-to-one]] or [[Introduction%20to%20EclipseLink%20JPA%20(ELUG)#@ManyToOne|many-to-one]] mapping in a Java SE environment that does not permit the use of <tt>-javaagent</tt> on the JVM command line, to configure EclipseLink JPA to perform lazy loading when annotation attribute <tt>fetch</tt> is set to <tt>javax.persistence.FetchType.LAZY</tt>, you can use static weaving. | ::When using a [[Introduction%20to%20EclipseLink%20JPA%20(ELUG)#@OneToOne|one-to-one]] or [[Introduction%20to%20EclipseLink%20JPA%20(ELUG)#@ManyToOne|many-to-one]] mapping in a Java SE environment that does not permit the use of <tt>-javaagent</tt> on the JVM command line, to configure EclipseLink JPA to perform lazy loading when annotation attribute <tt>fetch</tt> is set to <tt>javax.persistence.FetchType.LAZY</tt>, you can use static weaving. | ||
− | :Also, all the mapping types in the Mapping column of the "EclipseLink JPA Support for Lazy Loading by Mapping Type" were links to ELUG. I removed the links. | + | :Also, all the mapping types in the Mapping column of the "EclipseLink JPA Support for Lazy Loading by Mapping Type" were links to ELUG. I removed the links. For example: |
+ | ::[Introduction%20to%20EclipseLink%20JPA%20(ELUG)#@OneToMany|one-to-many |
Revision as of 15:35, 2 May 2011
-- Ben Gelernter 4/28/11
- ELUG ref
- I removed this reference to ELUG. Return here to see if this information needs to be brought forward into this doc.
- This was the last item in the first list, right after " What You May Need to Know About Weaving JPA Entities"
- More ELUG refs:
- These are the 3rd and 4th paras:
- When using a one-to-one or many-to-one mapping in a Java SE environment, to configure EclipseLink JPA to perform lazy loading when the fetch attribute is set to FetchType.LAZY, configure either dynamic or static weaving.
- When using a one-to-one or many-to-one mapping in a Java SE environment that does not permit the use of -javaagent on the JVM command line, to configure EclipseLink JPA to perform lazy loading when annotation attribute fetch is set to javax.persistence.FetchType.LAZY, you can use static weaving.
- Also, all the mapping types in the Mapping column of the "EclipseLink JPA Support for Lazy Loading by Mapping Type" were links to ELUG. I removed the links. For example:
- [Introduction%20to%20EclipseLink%20JPA%20(ELUG)#@OneToMany|one-to-many