You need to find out the root cause of that exception. It usually means a class is being used in a constructor, static initializer, or something similar and encountered an error.... basically the error was during the construction of an object probably. The reason it's happening when you try to use the bundle is most likely because you are accessing a lazily instantiated bean from your blueprint xml....
You need to find out what that root cause it to figure it out. Ryan On Mar 12, 2014 3:10 PM, "Kevin Carr" <kscar...@gmail.com> wrote: > In 2.3.x, a bundle works fine. When I try to run it in 3.0, anything that > uses that bundle get an error saying ClassNoDef error. > > Was there anything that would have changed how 3.0 resolves ClassPath? > > Anybody else run into this issue? > > -- > Scott Carr >
