On Fri, 2010-12-03 at 13:08 +0100, Roman Kennke wrote: > >> However, one question remains. Is there a way to distinguish between the > >> IOException thrown be >shutdown and other (i.e. protocol/network related) > >> IOException? As far as I can see, there is no >special subclass for > >> shutdown related IOException. > >> > >> Kind regards, > >> **Roman > >> > > > >Unfortunately, there does not seem to be a way. This is one of the > >limitations of the classic I/O model in Java. > > Couldn't you simply throw a specific subclass of IOException? Like NIO does > using the AsynchonousCloseException? >
This cannot be done 'simply'. Several classes likely need to be coupled with the connection class in order to make them aware of its internal state, which is something I am reluctant to do. Probably one might be able to get away with just decorating input / output streams of the underlying Socket, but I am not entirely sure it is really worth the trouble. Feel free to explore this possibility or some other and contribute a patch. Cheers Oleg > **Roman > > > This communication is for informational purposes only. It is not > intended as an offer or solicitation for the purchase or sale of > any financial instrument or as an official confirmation of any > transaction. All market prices, data and other information are not > warranted as to completeness or accuracy and are subject to change > without notice. Any comments or statements made herein do not > necessarily reflect those of JPMorgan Chase & Co., its subsidiaries > and affiliates. > > This transmission may contain information that is privileged, > confidential, legally privileged, and/or exempt from disclosure > under applicable law. If you are not the intended recipient, you > are hereby notified that any disclosure, copying, distribution, or > use of the information contained herein (including any reliance > thereon) is STRICTLY PROHIBITED. Although this transmission and any > attachments are believed to be free of any virus or other defect > that might affect any computer system into which it is received and > opened, it is the responsibility of the recipient to ensure that it > is virus free and no responsibility is accepted by JPMorgan Chase & > Co., its subsidiaries and affiliates, as applicable, for any loss > or damage arising in any way from its use. If you received this > transmission in error, please immediately contact the sender and > destroy the material in its entirety, whether in electronic or hard > copy format. Thank you. > > Please refer to http://www.jpmorgan.com/pages/disclosures for > disclosures relating to European legal entities. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
