[
https://issues.apache.org/jira/browse/FELIX-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374814#comment-16374814
]
Richard S. Hall commented on FELIX-5782:
----------------------------------------
Looking at this latest patch, it makes it a little more obvious to ask, why we
are creating lots of different exception classes as opposed to adding a single
extended exception with a "reason" method?
Especially, if in the future, you thought about adding more diagnostics (not
that we will want to or should) which would have to be duplicated across all of
these exceptions.
In general, I try to avoid creating lots of classes.
> allow resolver errors to be introspected
> ----------------------------------------
>
> Key: FELIX-5782
> URL: https://issues.apache.org/jira/browse/FELIX-5782
> Project: Felix
> Issue Type: Improvement
> Components: Resolver
> Reporter: Raymond Augé
> Assignee: Thomas Watson
> Priority: Minor
>
> The current model for resolver errors does not provide any means of
> introspecting deeper knowledge that the resolver gained. The information is
> internal only, which makes user feedback more difficult to produce than
> necessary.
> I propose to expose the error types by means of an exported package
> {{org.apache.felix.resolver.error}}. This will allow interested clients to
> dig more deeply into the reasons for resolution failure in order to provide
> better feedback to users.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
