| Problems when using ApsectJ and Gemini EclipseLink weaving for LazyLoading [message #1272172] |
Mon, 17 March 2014 08:54  |
 Jack Kilian
Messages: 40
Registered: March 2012 |
Member |
|
|
Hi,
I would like to combine EclipseLink Dynamic weaving with AspectJ custom Aspects.
E.g. my goal is to recognize when a setter of a Model class is called.
pointcut wrapJpaSetterMethods() : ( execution(void mypackage.model.*.set*(..))
My Problem is now, that this combination of AspectJ (Equinox weaving) and EclipseLink dynamic weaving log an warning when I use LazyLoading defined attributes like:...
@OneToOne(fetch = FetchType.LAZY, cascade = { CascadeType.PERSIST })
@JoinColumns({ @JoinColumn(name = "ID", referencedColumnName = "REF_ID", nullable = false, insertable = false, updatable = false), })
private MyClass myClass;
the message is due to this for all classes who are waved by my own AspectJ aspect:
Reverting the lazy setting on the OneToOne or ManyToOne attribute [myClass] for the entity class [class mypackage.model.MyClass] since weaving was not enabled or did not occur.
Any experience in the EclipseLink world?
Is this a problem of the weaving order - in other words if EclipseLink or AspectJ is the first weaver?
best regards
jk
[Updated on: Mon, 17 March 2014 08:54] Report message to a moderator |
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04473 seconds
] 
Search
Help
Register
Login
Home
