[ 
https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482741#comment-13482741
 ] 

Steve Gillam commented on LANG-769:
-----------------------------------

Disambiguation/Accuracy of the semantic (and, thus, its name) is key here - 
otherwise it will quickly lose it's worth and become a valid candidate for 
disappearing again (as any such should be).

Whilst Not(Un)Implemented is the most often created it does not communicate the 
semantic well and could well be confused with the permanent decision not to 
implement an optionalAPI call.

It somehow needs to represent itself (and, thus, the response (human/systemic) 
as being a function of the development lifecycle ('You told me you'd 
finished!'). Perhaps others cleverer than I can propose a succinct 
representation?

Obviously it needs to be a subclass of RuntimeException so we don't have to run 
around polluting 'completed' code with throws clauses :)
                
> Please restore NotImplementedException and UnhandledException
> -------------------------------------------------------------
>
>                 Key: LANG-769
>                 URL: https://issues.apache.org/jira/browse/LANG-769
>             Project: Commons Lang
>          Issue Type: Improvement
>          Components: lang.exception.*
>            Reporter: david cogen
>            Priority: Minor
>
> Why were these removed? I found these very useful and used them often. As the 
> version 2.6 api javadoc states, "This exception supplements the standard 
> exception classes by providing a more semantically rich description of the 
> problem."
> Just want you to realize that these have found direct use outside the 
> library; not just internal use within commons-lang.
> I will define these missing classes myself, or maybe include both 
> commons-lang and commons-lang3 (but I really don't to do that). It would be 
> very nice to have these back.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to