Wasn't NioProcessor made non-final as part of fixing DIRMINA-615 ? The attached patch file removes the final keyword.
At work I'm currently using a custom build of 2.0.0-M3 with just one change -- to remove the final keyword from NioProcessor. There's quite a lot of code in that class, copy pasting all of it to be able to add a specific catch clause to the read() and write() methods is a high price to pay. Using a custom build is pretty inconvenient too, and the maven project is no longer as easily distributable. > Yeah, they are final to (supposely) protect the developper from mis-using > them in an extended method > (which seems to me a bad choice, to some extent : either the user is > 'educated' or not, in any case, > those who want to extend those classes know what they are doing !). We may > reconsider that Please do. It'd be mighty helpful to me. Regards, Barend On Fri, Oct 24, 2008 at 10:03 AM, Barrie Treloar <[EMAIL PROTECTED]> wrote: > On Fri, Oct 24, 2008 at 4:39 PM, Johan Haleby <[EMAIL PROTECTED]> wrote: >> You could try out PowerMock (www.powermock.org), it allows you to mock final >> classes/methods easily if you're used to EasyMock. > > Nice! > > I will write up some tests then. >
