From: Andrew K. <ak...@Sm...> - 2003-02-06 14:00:31
|
It there any reason why the core code does not set the cause for BEEPException's raised? An issue I have is that a telnet connection to the BEEP server will cause the TCPSessionCreator to throw an execption, but I can't easily determine what the cause was, so I have to loop and recreate the TCPSessionCreator. while (keepRunning) { try { TCPSessionCreator.listen(listenPort, reg); } catch (BEEPException be) { log.error("BEEP exception thrown", be); } } Now if I run another instance of the server on the same port, I obviously get a BindException thrown internally, but I can't trap that as all I receive in the above code is a BEEPException with no cause set. This is one example but there are probably many other different situations, where the underlying cause might need to be available? |