Hi Mina-folks, we're using the trunk/2.0 version of mina in some of our apps. For test purposes I used a DummySession and mocked the write() and close()-methods with easyMock classextension, because I'm not interested in any other method calls, like get/setAttribute. Some of these Methods are called from the Statemachine or other sources and I don't want to change mock expectations everytime a library changes. Today we made an update and the test failed, or to be more specific: the mock didn't work as expected. After some investigation I found out that EasyMock couldn't mock the methods because *all* methods at the AbstractIoSession are final or private. An abstract class with just final and private methods looks very odd to me. Normally, if you declare a class abstract it means to me that I can extend its functionality for my own use. But this isn't given anymore if you declare all methods final. I think that this will lead into lots of copies with the name "MyAbstractIoSession", just because people wants to extend the AbstractIoSession functionality. Can someone explain me the reason of the change, because I can't see any (maybe I'm blind 8-) ). Or do you have any ideas how to solve this without writing a new DummySession from sratch?
regards from Germany, Steve ps: The revision of the "final change" is 597545 pps: The framework is very nice, so keep on going! -- View this message in context: http://www.nabble.com/final-AbstractIoSession-tf4889613s16868.html#a13996006 Sent from the Apache MINA Support Forum mailing list archive at Nabble.com.
