I think this was an earlier issue that was fixed. What version are you
using, and can you check if this issue still occurs in the latest build?
Adam Bien wrote:
>
> Hi All,
>
> it seems like in the following scenario:
>
> @OneToOne(cascade=CascadeType.ALL,fetch=FetchType.LAZY)
> private Detail lazyDetail;
>
> @OneToOne(cascade=CascadeType.ALL,fetch=FetchType.EAGER)
> private Detail eagerDetail;
>
> the weaver (Ant-Task) ignores the FetchType.EAGER and processes the
> "eagerDateil" relation as well.
> We encountered some problems in the application and found both relations
> with the "weaved" indirection (I attached the screenshot).
> In my opinion the weaver should only process "LAZY" attributes?
>
> Any thoughts?
>
> thank you in advance,
>
> adam
>
-----
---
http://wiki.eclipse.org/User:James.sutherland.oracle.com James Sutherland
http://www.oracle.com/technology/products/ias/toplink/ Oracle TopLink ,
http://www.eclipse.org/eclipselink/
EclipseLink , https://glassfish.dev.java.net/javaee5/persistence/ TopLink
Essentials
Wiki: http://en.wikibooks.org/wiki/Java_Persistence Java Persistence ,
http://wiki.eclipse.org/EclipseLink EclipseLink
Forums: http://forums.oracle.com/forums/forum.jspa?forumID=48 TopLink ,
http://www.nabble.com/EclipseLink-f26430.html EclipseLink ,
http://www.nabble.com/java.net---glassfish-persistence-f13455.html Glassfish
Persistence
--
View this message in context: http://www.nabble.com/Understanding-of-Static-Weaving-tf4836623.html#a13838442
Sent from the java.net - glassfish persistence mailing list archive at Nabble.com.