Re: [Springframework-developer] EclipseLink

[Juergen H. <jue...@sp...>]

Magnus,

 

I have removed that configuration option from PetClinic because I've found
issues with EclipseLink's class file transformer on Tomcat load-time
weaving. EclipseLink works fine in our integration tests within the main
framework test suite, so this is not a general judgement of EclipseLink by
any means. We'll try to resolve the load-time weaving issues together with
the EclipseLink guys.

 

Juergen

 

 

  _____  

From: spr...@li...
[mailto:spr...@li...] On Behalf
Of Magnus Heino
Sent: Thursday, February 28, 2008 9:01 AM
To: spr...@li...
Subject: [Springframework-developer] EclipseLink

 


Hi. 

I just noticed that Juergen checked in a change with this comment:

"removed commented-out EclipseLink configuration - to be reintroduced after
further testing "

http://fisheye1.cenqua.com/changelog/springframework?cs=MAIN:jhoeller:200802
27214817

What does that mean? Are there known bugs in EclipseLink, in the EclipseLink
Spring adapters, or is it because of  Petclinic not been properly tested
whith EclipseLink and it's now time for a 2.5.2 release? 

We are about to try out EclipseLink in Spring in a few days, and it would be
nice to know if we should rethink that already...


-- 

 /Magnus Heino