[jira] [Commented] (EMPIREDB-99) Remove optional support for old style error handing

["Rainer Döbele (JIRA)" <em...@incubator.apache.org>]

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

Rainer Döbele commented on EMPIREDB-99:
---------------------------------------

The removal of the old style error handling will be the biggest API change since we entered incubation and thus it will affect backwards compatibility for code that is currently not using exceptions.
Ideally code that is currently using exceptions (ErrorObject.setExceptionsEnabled(true)) - like the examples - should still work without changes if possible.

Basically we need to remove the class ErrorObject and change all Boolean return values to void. But this probably sounds easier as it is. However I would like to keep the EmpireException and the error type definition (ErrorType) as it is.

Once the core is changed, the most difficult task will probably be to apply the changes to the empire-struts2-extentions.


> Remove optional support for old style error handing
> ---------------------------------------------------
>
>                 Key: EMPIREDB-99
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-99
>             Project: Empire-DB
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Rainer Döbele
>            Assignee: Rainer Döbele
>             Fix For: empire-db-2.2.0-incubating
>
>
> For error handling we can currently switch between Exception-mode and an exception-less mode with Boolean return values for most functions to indicate an error. This exception-less mode ist old fashioned and not needed any more. 
> It should be removed from the API which also means that most function returning boolean values will need be declared as void. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira