I need another advice about the method names of the ExceptionContext.
Currently the interface defines methods like
interface ExceptionContext {
addValue(...);
setValue(...);
getValues(...);
...
};
Looks fine at first glance. However, if I create a ContextedNamingException
I will have
class ContextedNamingException extends Exception implements ExceptionContext
{
getRemainingName(...);
getResolvedName(...);
setRemainingName(...);
setResolvedName(...);
...
addValue(...);
setValue(...);
getValues(...);
...
};
Since the ExceptionContext is especially designed for an exception mix-in, I
wonder if we better use more qualifying names for this use case:
interface ExceptionContext {
addContextValue(...);
setContextValue(...);
getContextValues(...);
...
};
Opinions?
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
