| weaving errors with eclipseLink 2.6.2 [message #1730021] |
Thu, 21 April 2016 00:17 |
 Bruce Conrad
Messages: 11
Registered: July 2009 |
Junior Member |
|
|
After upgrading to eclipseLink 2.6.2 from 2.4.1 I began receiving weaving errors, persistence_shallow_clone, when running my unit tests. (I got same with 2.5.2). It seems to run fine in my weblogic container but haven't fully tested. I was able to get rid of the errors by setting property eclipselink.weaving to false in my persistence.xml file. I also have some weaving settings in my spring applicationContext.xml (below)
So, I'm wondering if weaving is really turned on by Spring and eclipseLink 2.6.2 got more strict. How can I tell if weaving is really happening. If it is a real error, what do I need to do to fix it? Again, this all worked with eclipseLink 2.4.1.
Spring applicationContext.xml configuration file (v 4.2.2):
<context:load-time-weaver />
<bean id="appManEntityManagerFactory"
class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
<property name="dataSource" ref="cmtDS" />
<property name="persistenceXmlLocation" value="classpath:/META-INF/appmanPersistence.xml" />
<property name="jpaVendorAdapter">
<bean
class="org.springframework.orm.jpa.vendor.EclipseLinkJpaVendorAdapter">
<property name="showSql" value="false" />
</bean>
</property>
<property name="loadTimeWeaver">
<bean
class="org.springframework.instrument.classloading.InstrumentationLoadTimeWeaver" />
</property>
</bean>
[Updated on: Thu, 21 April 2016 00:23] Report message to a moderator |
|
|
Powered by
FUDForum. Page generated in 0.03099 seconds
] 
Search
Help
Register
Login
Home
