RE: [OJB-developers] superflous CriteriaException

[Bischof, R. <rai...@ed...>]

Thomas,


>> BTW:
>> I keep running into traps where Exceptions are silently ignored. I
>> guess this should change but that would lead to lots of API changes as
>> methods have to declare Exceptions that they haven't thrown before.
>> This would also lead to lots of small modifications to many classes,
>> so I guess this can only be done by you as it will be too much work to
>> integrate many small changes into your concurrently changing codebase.
>> Or we need a code-freeze for some time after the next release so that
>> a volunteer can do it.
>> 
>> What do you think?
>> 

>This cleanup is already on the todo list. I will try to it without
>changes to the PersistenceBroker API. 
>I agree that it will be easier to do this myself than to delegate it and
>to reintegrate the results...

From my point of view API changes are justified if they lead to a better
useability. Especially these chnages only mean throwing Exceptions where
they haven't been thrown before. I know this leads to code changes in
existing applications but that's something we have to live with in order to
enhance reliability which should be the main focus. It's just that IMHO OJB
has a limited reliability if it just ignores Exceptions which arise
somewhere in the framework.

Another point - next feature request ;-) :
What about adding a method to the Broker which deletes objects that match a
query ( & again SQL statement).
Right now it's somewhat tedious to cycle through a collection and delete all
obecjts by hand. The broker can even optimize this if the descriptor
indicates that affected objects have no dependend objects it can directly
issue a delete statement without instantiating all objects (needs to clear
the cache for this class, though).

Thanks,
rb

Rainer Bischof
EDS - Electronic Data Systems
European Automotive Solution Center - Distributed Solutions
Email: rai...@ed...