I believe Martin just added to the docs earlier today covering the property that affects this. The better solution is to have torque throw runtime exceptions except in cases where it is fairly certain the application code can use the exception constructively. Since it may be desirable for torque objects to implement interfaces, it is better to have the generated methods unencumbered by named exceptions.
I know the TorqueException/Exception problem occurs because of differences in exceptions between the fulcrum security api and torque. I can't remember the details on why Exception is better, but there was a problem. john mcnally On Fri, 2002-11-15 at 10:11, Daniel Rall wrote: > Quinton McCombs <[EMAIL PROTECTED]> writes: > > > You can view the issue detail at the following URL: > > <http://nagoya.apache.org/scarab/issues/id/TRQS70> > > > > Type : Defect > > Issue Id : TRQS70 > > Reported by: Quinton McCombs > > quintonm - ([EMAIL PROTECTED]) > > > > Details: > > > > Summary: Generated code for save() throws Exception and not TorqueException > > Description: Generated "om" code for the save() method throws Exception while the >other save methods throw TorqueException > > Status: New > > John, you want to answer this one? > -- > > Daniel Rall <[EMAIL PROTECTED]> > > -- > To unsubscribe, e-mail: <mailto:turbine-torque-dev-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: <mailto:turbine-torque-dev-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:turbine-torque-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:turbine-torque-dev-help@;jakarta.apache.org>
