On 13/07/2008, at 11:23 PM, Mike Schrag wrote:
>> a couple of suggestions for consistency + reuse. It'd be worth
>> making more use of ERXEOControlUtilities. e.g.,
>> a) fetch<Entity> throws IllegalStateException if multiple records
>> are found rather than EOUtilities.MoreThanOneException as does
>> ERXEOControlUtilities.objectForQualifier and EOUtilities.
>> b) fetchRequired throws NoSuchElementException rather than
>> EOObjectNotAvailableException as does
>> ERXEOControlUtilities.requiredObjectForQualifier let alone
>> EOUtilities.
>> c) creating a record for relation... again make use of
>> ERXEOControlUtilities.
> Yeah I know ... This is all historical. These templates come from
> before my Wonder life. Now I'm hesitant to change the exceptions
> that are thrown because they're not checked exceptions, so if people
> are catching them explicitly, things will break with no way of
> knowing they break at compile time (checked exceptions: 1, unchecked
> exceptions: 0).
Perhaps we could use a veogen property to allow for backwards
compatibility?
with regards,
--Lachlan Deck
This archive was generated by hypermail 2.0.0 : Tue Jul 15 2008 - 03:51:09 EDT