Hi Guillaume,
Deployment works fine for me, as soon as I remove some
dependencies from the pom
Which dependencies should I remove please ?
(servicemix-* should all be at
provided scope).
servicemix-jbi and -core are both duplicated in my pom - one has scope
"provided".
I think I have cleaned this up, but I still seem to be getting problems
- such as :
Caused by: java.lang.NoClassDefFoundError
at
org.hibernate.proxy.CGLIBLazyInitializer.getProxyFactory(CGLIBLazyInitializer.java:116)
... 20 more
8/01/2007 16:20:47 org.apache.commons.logging.impl.SLF4JLog error
SEVERE: CGLIB Enhancement failed:
org.apache.ode.daohib.bpel.hobj.HCorrelator
java.lang.NoClassDefFoundError
at
org.hibernate.proxy.CGLIBLazyInitializer.getProxyFactory(CGLIBLazyInitializer.java:116)
at
org.hibernate.proxy.CGLIBProxyFactory.postInstantiate(CGLIBProxyFactory.java:41)
at
org.hibernate.tuple.PojoEntityTuplizer.buildProxyFactory(PojoEntityTuplizer.java:161)
at
org.hibernate.tuple.AbstractEntityTuplizer.<init>(AbstractEntityTuplizer.java:131)
at
org.hibernate.tuple.PojoEntityTuplizer.<init>(PojoEntityTuplizer.java:55)
at org.hibernate.tuple.TuplizerLookup.create(TuplizerLookup.java:64)
(I am using the SVN head version of servicemix) ....
I would be very grateful for any suggestions ...
Thanks,
Roger
On 1/8/07, Roger Menday <[EMAIL PROTECTED]> wrote:
Hi Matthieu,
Is it possible to add the migration to OpenJPA to the JBI module as
well ?
I'm trying to deploy the latest ODE to servicemix and getting a number
of hibernate exceptions, and I don't know where to start to make them go
away.
thanks !
Roger
> Hi all,
>
> The world as you know it has just changed. Well, at least some part of
> it.
> I've just committed the change in ODE from Hibernate to OpenJPA so now
> the
> WAR produced by the build uses OpenJPA by default. It seems to work
> properly
> from what I've tried. I have a feeling that it's not using the
> transaction
> manager properly yet and it's in autocommit but I'm not quite sure, I
> still
> have to work on that. But most processes should work anyway.
>
> In case of emergency, you can set the system property
> 'ode.persistence' to
> 'hibernate' and it will switch back to Hibernate after a restart. But
> if you
> find a bug, fixing it or yelling would be better anyway.
>
> Last but not least, I had to fight a lot with Maven to get things
roughly
> working. However the enhancement of persistence classes in the
bpel-store
> won't work if you run a global build. You will have to build
bpel-store
> individually first and then build everything. For some reason
> maven.plugin.classpath doesn't get set properly when doing a reactor
> build,
> if somebody knows a workaround, that would be great.
>
> Thanks to Lance for doing most of the JPA migration work!
>
> Matthieu
>
