Kevin, if you submit a performant patch that catches this situation,
I'm sure we'll apply it. It's standard practice in DataContext to
check the validity of the arguments in the public API.
On 9/14/05, Kevin Menard <kmenar..ervprise.com> 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
This archive was generated by hypermail 2.0.0 : Wed Sep 14 2005 - 16:12:05 EDT