aa78d49de1
IdleStateEvent is very convenient and frequently used type of events. However both in runtime (logs) and in debug you need some manual steps to see their actual content. Default implementation generates worthless trash like this: io.netty.handler.timeout.IdleStateEvent@27f674d There are examples already, where event has convenient and useful toString implementation: * io.netty.handler.proxy.ProxyConnectionEvent * io.netty.handler.ssl.SslCompletionEvent * Implement 'IdleStateEvent.toString' method. * Unit test. More useful String representation of IdleStateEvent |
||
---|---|---|
.. | ||
src | ||
pom.xml |