You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@daffodil.apache.org by "Brandon Sloane (JIRA)" <ji...@apache.org> on 2019/03/18 18:20:00 UTC

[jira] [Created] (DAFFODIL-2100) Error handling some parseErrors

Brandon Sloane created DAFFODIL-2100:
----------------------------------------

             Summary: Error handling some parseErrors
                 Key: DAFFODIL-2100
                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2100
             Project: Daffodil
          Issue Type: Bug
          Components: Back End
            Reporter: Brandon Sloane
            Assignee: Brandon Sloane


ProcessingError.toParseError erronausly passes itself as the maybeCause. Compare its definition with that to toUnparseError:

 

{{def toParseError = new ParseError(schemaContext, dataContext, Maybe(this), maybeFormatString, args: _*)}}

def toUnparseError = new UnparseError(schemaContext, dataContext, maybeCause, maybeFormatString, args: _*)

 

This is particuarly problamatic because ParseError requires one of the maybeFormatString and maybeCause may be defined. If maybeFormatString is defined, then they both would be within ParseError, so no useful error will be reported.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)