From: Joakim O. <joa...@ag...> - 2007-03-23 14:26:28
|
> > Which version of java are you running? > > 1.4.2 No problems there, good > > Do you have any other versions of CGLIB on your class path than the > > one bundled with rMock? > > Not that I can find. Ok, that one out of the picture. > > Which version of spring are you using? > > 1.2.8 Ok, at my current assignment we run 1.2.5 without problems so I don't think that there is a problem there. I can't tell wether signing the jars would have this impact (you do sign the Spring jars yourself right or are there signed jars to download from Springs site? > I have this same problem trying to mock my own classes (at least under RC5). Ok, did you run any version of rMock before RC5 that did not show this problem? > 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. > Weird, does not sound good. I guess you don't package those into signed jars before you run your tests right? I know that one thing that we released in 2.0.0 is a custom cglib naming-policy. Perhaps that confuses the security manager when that package is signed... If that is the case we may be able to make that one optional. > > 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. As soon as we have the example we will do our best to come up with something promptly. Thank you for your cooperation on this issue. /Joakim Ohlrogge |