|
From: David C. <dc...@al...> - 2007-03-23 14:09:14
|
On Friday 23 March 2007 08:31, Joakim Ohlrogge wrote: > Hi David, > > When I dig deep down in the stacktrace this comes up: > > Caused by: java.lang.SecurityException: > > class "org.springframework.context.ApplicationContextMock"'s signer > > information does not match signer information of other classes in the > > same package > > at java.lang.ClassLoader.checkCerts(ClassLoader.java:611) > > at java.lang.ClassLoader.defineClass(ClassLoader.java:532) > > ... 38 more > > Do you run the tests under a security manager? Not conciously. I"m just running it inside eclipse. Our production code does (webstart) and all of jars are signed. > Which version of java are you running? 1.4.2 > Do you have any other versions of CGLIB on your class path than the > one bundled with rMock? Not that I can find. > > I'm thinking that the problem may be related to the fact that rMock > generates dynamic classes when you mock a class. That could confuse a > security manager if it's currently running under a policy. > > Which version of spring are you using? 1.2.8 > > Is it possible for you to mock the BeanFactory-interface instead of a > class? Does that change anything? I have this same problem trying to mock my own classes (at least under RC5). With 2.0, a whole bunch of tests started failing that I'm not familiar with. I'll re-verify that with 2.0, I still have problems with *my* classes to keep things simple. > It would help us a lot if you could isolate the problem to something > that we can easily run on our side in order to be able to track this > one down. A reasonable request. I'll work on it. > > I'm sorry that I can only give you questions at this time. > David |