Bug 318696

Description Umesh 2010-07-02 07:17:10 EDT

Build Identifier: Spring 2.5.4

Hi,

We are trying to achieve load time weaving of our JPA classes using Spring Framework's InstrumentationLoadTimeWeaver on Websphere. 

On Weblogic, we were able to achieve this successfully using Spring's WebLogicLoadTimeWeaver. 

Since Websphere doesn't have an equivalent, we are using InstrumentationLoadTimeWeaverand starting the application with the -javaagent parameter specified. 
This creates 2 different versions of the same class within the JVM (one instrumented and another non-instrumented) which are incompatible with each other causing exceptions while trying to do any database action like read, insert, etc.

Is there a set of guidelines or steps available to achieve this instrumentation without such errors?

Out entityManager definition in spring looks like:

<bean id="entityManagerFactory" 
class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
<property name="persistenceUnitName" value="ds"/> <property name="dataSource" ref="dataSource"/> <property name="jpaVendorAdapter"> <bean class="org.springframework.orm.jpa.vendor.EclipseLinkJpaVendorAdapter">
<property name="showSql" value="false"/> <property name="generateDdl" value="false"/> </bean> </property> <property name="loadTimeWeaver"> <bean class="org.springframework.instrument.classloading.InstrumentationLoadTimeWeaver"/>
</property>
</bean>

This project is already on critical path. Any early reply / help is appreciated.

Thanks
Umesh


Reproducible: Always

Steps to Reproduce:
1.Deploy any application using JPA  on websphere.
2.
3.