It's also hard to do. :)
I think any patches to improve the descriptiveness of error messages
(and/or the depth of exceptions) would be greatly appreciated.
However, I'm not entirely sure Kevin's problem could have been solved
by better exception handling.
On 9/14/05, Gili <cowwo..bs.darktech.org> wrote:
>
> +1000 on this point. I still can't say whether Cayenne suffers from
> this problem or not but Hibernate sure did. It is *vital* that
> exceptions be as descriptive and helpful as possible. It saves countless
> hours of troubleshooting.
>
> Gili
>
> Kevin Menard wrote:
> >
> > On Sep 14, 2005, at 10:00 AM, Cris Daniluk wrote:
> >
> >> When setDataContext() is called, the DataContext should know its going
> >> to be holding the CDO. Couldn't setDataContext check the object store
> >> and see if the CDO is already in there. Then it could throw an
> >> exception if not, preventing the confusing situation...
> >
> >
> > I would be fine with this.
> >
> > I really like Cayenne, but more often than I'd like I find myself
> > spending hours tracking down problems. It's usually my fault they
> > happened in the first place, but something like this simple exception
> > here could save hours. I hate to keep drawing comparisons to Tapestry,
> > but I guess I really like what they do so I look to them as a model.
> > Tapestry is not an extremely simple framework to use, but they make
> > their error messages as descriptive as possible and it really goes a
> > long way.
> >
> > --
> > Kevin
>
> --
> http://www.desktopbeautifier.com/
>
This archive was generated by hypermail 2.0.0 : Wed Sep 14 2005 - 10:23:01 EDT