> This is precisely the reason why I changed JBookTraderException to > extend RuntimeException, rather than a checked exception. It's because > what was happening before is that JBookTraderException was re-thrown > up the caller stack, because there was no reasonable way to recover > from it. I am willing to debate this, though.
Right, but in reality the general practice is that you never declare a domain exception to extend RuntimeException, since it's not a checked exception and it's not recoverable, why do you bother to have a subclass(you are not gonna to check it, right?), why don't you just use RuntimeException directly? Also in our code, we are recoverable from many places from my opinion, and at least we want to notify users about them (i.e. MainFrameController, StrategyTableModel, TradingSchedule etc.), making JBookTraderException a runtime exception surely wouldn't do us any good in these cases. My suggestion is that we should still have our domain exception, and for those un-recoverable special cases we should just use RuntimeException directly. What do you think? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JBookTrader" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jbooktrader?hl=en -~----------~----~----~----~------~----~------~--~---
