Ok

Analysis was right but fix was wrong, we (i can assume it ;) commented out
our javaagent to build on early java 7 with openjpa but it is better now
and we can activate it back. Result: we have the enhancement for free (hard
part was to get openjpa config right, needed too much openjpa internals to
do it before the emf is created + some more file dumps).

Trunk has still some failures but seems clearly manageable now.

We should be stable again soon :)
 Le 16 juil. 2014 00:10, "Romain Manni-Bucau" <[email protected]> a
écrit :

> Hey guys
>
> started to work on current failures, seems we need to force openjpa
> enhancement for cmp beans (can't be done at build time since we
> generate them).
>
> here my draft patch:
> https://gist.github.com/rmannibucau/8da6c9a0d62f58f37270
>
> mvn test -Dtest=iTest doesn't pass yet (seems it fails but enhancement
> is done (didn't check cause it is late but can also just be the
> exception which changed ... but I guess that's a conflict between
> business methods and JPA part, we can desire to enhance the
> mapping.xml file for this pupose to ignore in JPA some methods, to be
> checked).
>
> If anyone wants to go ahead with it to see if we solve our issues this
> way it would be awesome otherwise I can try to continue in the week.
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>

Reply via email to