james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefano Bagnara (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] Created: (MIME4J-172) Define how to deal with parsing error while building the DOM (ParsedField.isValid/getParseException seems unintuitive: anything better?)
Date Sat, 30 Jan 2010 21:39:34 GMT
Define how to deal with parsing error while building the DOM (ParsedField.isValid/getParseException
seems unintuitive: anything better?)
----------------------------------------------------------------------------------------------------------------------------------------

                 Key: MIME4J-172
                 URL: https://issues.apache.org/jira/browse/MIME4J-172
             Project: JAMES Mime4j
          Issue Type: Task
          Components: project
    Affects Versions: 0.6
            Reporter: Stefano Bagnara
             Fix For: 0.8


ParsedField interface has "isValid" and "getParseException": from the DOM perspective a field
should always be valid, shouldn't it? Shouldn't we throw exception during parsing instead
of building the dom node with "isValid"/"getParseException" methods? Can you provide an use
case where an exception/monitor during parsing is not enough and we need to carry the "invalidity"
to the DOM? 
(extracted from MIME4J-156 comments)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message