| EclipseLink weaver agent or Spring agent [message #389403] |
Wed, 03 June 2009 19:20  |
Eclipse User |
|
|
|
I have dynamic weaving working in an EclipseLink standalone environment
but now I want to enable dynamic weaving in EclipseLink 1.1.1 within a
Spring 2.5.6 environment.
Can I still use the EclipseLink weaving agent or do I need to use Spring's
weaving agent instead of EclipseLink?
In my persistence.xml I have these properties set:
<property name="eclipselink.weaving" value="true"/>
<property name="eclipselink.weaving.lazy" value="true"/>
And in my Spring applicationContext.xml I have this property set:
<context:load-time-weaver aspectj-weaving="on" />
but I'm wondering which option I should use for the load time weaving
class:
Currently I'm using this:
<bean id="entityManagerFactory"
class=" org.springframework.orm.jpa.LocalContainerEntityManagerFacto ryBean ">
<property name="persistenceUnitName" value="myunit" />
<property name="loadTimeWeaver">
<bean
class=" org.springframework.instrument.classloading.InstrumentationL oadTimeWeaver "
/>
</property>
</bean>
I tried setting the class to:
org.eclipse.persistence.internal.weaving.PersistenceWeaver
but got an exception from Spring that there was no default constructor
So, when integrating Spring with EclipseLink do I have to use the Spring
InstrumentationLoadTimeWeaver class?
Note I don't want to use the app server based weavers - I'm doing this in
standalone JSE 6 environment
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05221 seconds
Home