You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Steve Lawrence (Jira)" <ji...@apache.org> on 2022/08/16 15:21:00 UTC

[jira] [Updated] (DAFFODIL-2721) Standardize InfosetInputter and InfosetOutputter error handling

     [ https://issues.apache.org/jira/browse/DAFFODIL-2721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Lawrence updated DAFFODIL-2721:
-------------------------------------
    Priority: Critical  (was: Major)

> Standardize InfosetInputter and InfosetOutputter error handling
> ---------------------------------------------------------------
>
>                 Key: DAFFODIL-2721
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2721
>             Project: Daffodil
>          Issue Type: Bug
>            Reporter: Steve Lawrence
>            Priority: Critical
>
> The API for InfosetInputetr and InfosetOutputter is not well defined. In the InfosetOutputter API we have deprecated the use of the boolean return values, but have not changed the actual API.
> In both cases, implementations are expected to throw exceptions to report errors.
> In the InfosetOutputter, we catch all Exceptions and convert them to an SDE.
> In the InfosetInputter catches various kinds of exceptions based on InvalidInfosetExcpetion, but only documents NonTextFoundInSimpleContentException. It's not clear if try/catch'es wrap all calls to the InfosetInputter.
> We should double check that everything is correct. We may also want to create a specific exception for both the inputter and outputter that are consistent in naming (e.g. InfosetInputterException/InfosetOutputterException) and use these correctly and consistently.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)