Oh, **** this error was hellish... Ok, first of all thank you very very much for your help. Further more smx 3.3.x and ode branch 1.x and trunk work well in combination with java6.
My problem was that I used... mvn jbi:projectDeploy -DforceUpdate=true ...to deploy the components. Since servicemix-shared is a reference of the sus I've wrote it overwrites the already loaded servicemix-shared from hotdeploy... Ode already loads DefaultComponent from servicemix-shared but not ResolvedEndpoint. Reloading the library means that DefaultComponent and ResolvedEndpoint does no longer match which leads to the ClassNotFoundException... Hurray -.- Ok, smx4 solves this issue completely by using OSGi at its roots. I don't think that there's a fix for this issue in smx3 at all!? Conclusion: Never ever use jbi:projectDeploy with the -DforceUpdate=true param as long as u exactly know what side effects this can cause... (or use smx4 :)) Andreas On Thursday 08 October 2009 21:32:17 Rafal Rusin wrote: > Well, without the concrete example it's hard to say anything. > But I must say that I wouldn't expect SMX 3.3.1 + ODE 1.X works on > Java 6. So you can try 1.5 instead. > You can also run jbi tests and see if they work on your machine. To do > this, go to jbi dir and type > buildr _1.2.10_ clean test > > Regards, >
