Felix Meschberger wrote:
Makes absolute sense, except for throwing the RuntimeException as you
noted in your own follow-up.
And yes, I agree, this would require a big code review. On the other
hand taking the pragmatic approach of fixing those places one after the
other as the issues are encountered is probably the more feasible
approach ...
Well, if the logging is removed from loadBundle() we would have to change all
callers. Otherwise we might end up with exception not be logged at all.
But I like Thomas approach better anyway ;)
Cheers,
Christoph
