> > So do we switch TorqueException to a runtime exception and drop
> > TorqueRuntimeException which I don't think is being used much? Or
> > switch from TorqueException to TorqueRuntimeException?
>
>
> I favor the idea of TorqueException subclassing RuntimeException,
> but can't figure out exactly why.
I'd actually before TorqueRuntimeException. To me, it's more descriptive
of is actually happening. And with many Java newbies playing with Torque
and getting confused, I think the more we can spell out what is
happening, the better.
Also, in the app I'm working on, we used to always catch misc./runtime
exceptions via:
try
{
...
}
catch (Exception e)
{
...
}
But having the blanket catch Exception really gets on our nerves and
we'd like to move to:
try
{
...
}
catch (RuntimeException e)
{
...
}
They are very often the same thing and it looks just like a name change,
but we just like it better, as it insinuates we're doing all we can
catching for checked exceptions and what not and only doing the blanket
approach to exceptions that really deserve the blanket approach.
- Stephen
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
