You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Dave Thompson (Jira)" <ji...@apache.org> on 2023/02/01 12:23:00 UTC
[jira] [Closed] (DAFFODIL-2390) Handle Exceptions from SAXInfosetOutputter's contentHandler Calls
[ https://issues.apache.org/jira/browse/DAFFODIL-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave Thompson closed DAFFODIL-2390.
-----------------------------------
Commit f836f33b9a76ef4c18a25f30b8844ea99b19f11e changes were verified under DAFFODIL-2721.
Verified that commit f836f33b9a76ef4c18a25f30b8844ea99b19f11e addressed this issue. Verified that commit did remove try/catches from the SAXInfosetOutputter and updated the InfosetWalker to handle exceptions.
> Handle Exceptions from SAXInfosetOutputter's contentHandler Calls
> ------------------------------------------------------------------
>
> Key: DAFFODIL-2390
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2390
> Project: Daffodil
> Issue Type: Bug
> Components: API, Back End, SAX
> Reporter: Olabusayo Kilo
> Assignee: Steve Lawrence
> Priority: Major
> Fix For: 3.5.0
>
>
> Currently the code, ctaches any errors from the contenthandler call but doesn't do anything with it.
> We need to consider if there is something that needs to be done, or can be done, with these exceptions.
> So if something goes wrong in any InfosetOutputter, we are going to just keep on going and ignore that. We need to ensure that the results of InfosetOutputter functions are actually used and that there is some way to pass back information so that diagnostics about the failure can be recovered.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)