jgenender wrote: > > Hey guys, > > I was hoping to see if we could discuss some of the "final" qualifiers > on some of the methods in the AbstractIOSession. The reason I ask is it > would be cool to be able to override some of the methods such as: > > public WriteFuture write(Object message) > public final int getScheduledWriteMessages() >
I got the same problem some time ago. I "resolved" it with an IoFilter but I'm not very happy with it, because the code should be be like: call method X and expect it to call IoSession.write with object Y but it is like: call method X and expect it to call (IoSession.write which has to call) IoFilter.filterWrite with a WriteRequest with message object Y while the part in braces is implicit and therefore not intuitive. jgenender wrote: > > To be able to write MockObjects for unit tests of code. Any thoughts on > making these protected instead of final? > No, protected is wrong. I want to call the write method from another class in another package so it must be public. ;-) regards Steve -- View this message in context: http://www.nabble.com/AbstractIoSession-and-final-qualifiers-tp14507695s16868p14574837.html Sent from the Apache MINA Support Forum mailing list archive at Nabble.com.
