You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mime4j-dev@james.apache.org by "Stefano Bagnara (JIRA)" <mi...@james.apache.org> on 2010/01/30 22:39:34 UTC
[jira] Created: (MIME4J-172) Define how to deal with parsing error
while building the DOM (ParsedField.isValid/getParseException seems
unintuitive: anything better?)
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.