On Jan 2, 2004, at 6:36 PM, David Jencks wrote:
So, is the conclusion that canStart should check internal consistency but not talk to the outside world, and if a problem occurs in the outside world in doStart we throw a RuntimeException, and expect to get into the failed state?
That is what happens, but I'm not confident this is what should happen. I think it is but someone could easily argue for a different behavior.
Is there any particular reason we would or wouldn't want a specific declared exception here?
An exception is not expected here, so I don't know what we would gain. We could allow Exception but that seems just as bad. Again, I don't know what the best way to do this is.
-dain
