You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Jukka Zitting (JIRA)" <se...@james.apache.org> on 2007/05/17 22:37:16 UTC
[jira] Created: (MIME4J-16) Allow exceptions from a ContentHandler
Allow exceptions from a ContentHandler
--------------------------------------
Key: MIME4J-16
URL: https://issues.apache.org/jira/browse/MIME4J-16
Project: Mime4j
Issue Type: Improvement
Reporter: Jukka Zitting
There is currently no good way for a Mime4j ContentHandler to indicate that it has failed to process a message event and that no further events should be generated. Compare this with for example the SAX ContentHandler interface that allows implementing classes to throw SAXExceptions.
Being able to throw such processing exceptions is important for example for a handler that wants to incrementally store a message in a backend store like a relational database or a JCR content repository.
My proposal is to add a new MimeException exception class and allow it to be thrown from any of the ContentHandler methods. Such a change would be incompatible with any parser and other classes that call the ContentHandler methods (even indirectly, for example through the MimeStreamParser class), but existing classes that implement the ContentHandler interface would not be affected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Updated: (MIME4J-16) Allow exceptions from a ContentHandler
Posted by "Jukka Zitting (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/MIME4J-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated MIME4J-16:
--------------------------------
Attachment: MimeException.patch
Forgot to include src/test changes in the patch, here's an updated version.
> Allow exceptions from a ContentHandler
> --------------------------------------
>
> Key: MIME4J-16
> URL: https://issues.apache.org/jira/browse/MIME4J-16
> Project: Mime4j
> Issue Type: Improvement
> Reporter: Jukka Zitting
> Assigned To: Norman Maurer
> Fix For: 0.4
>
> Attachments: MimeException.patch, MimeException.patch
>
>
> There is currently no good way for a Mime4j ContentHandler to indicate that it has failed to process a message event and that no further events should be generated. Compare this with for example the SAX ContentHandler interface that allows implementing classes to throw SAXExceptions.
> Being able to throw such processing exceptions is important for example for a handler that wants to incrementally store a message in a backend store like a relational database or a JCR content repository.
> My proposal is to add a new MimeException exception class and allow it to be thrown from any of the ContentHandler methods. Such a change would be incompatible with any parser and other classes that call the ContentHandler methods (even indirectly, for example through the MimeStreamParser class), but existing classes that implement the ContentHandler interface would not be affected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [jira] Commented: (MIME4J-16) Allow exceptions from a ContentHandler
Posted by Stefano Bagnara <ap...@bago.org>.
Norman Maurer ha scritto:
> Im whould prefer to release mime4j first..
>
> WDYT ?
+1
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [jira] Commented: (MIME4J-16) Allow exceptions from a ContentHandler
Posted by Norman Maurer <no...@apache.org>.
Im whould prefer to release mime4j first..
WDYT ?
bye
Norman
Norman Maurer (JIRA) schrieb:
> [ https://issues.apache.org/jira/browse/MIME4J-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496804 ]
>
> Norman Maurer commented on MIME4J-16:
> -------------------------------------
>
> I like the idea... The question is should we apply the patch before tagging the svn for 0.3 release or after ?
>
>
>> Allow exceptions from a ContentHandler
>> --------------------------------------
>>
>> Key: MIME4J-16
>> URL: https://issues.apache.org/jira/browse/MIME4J-16
>> Project: Mime4j
>> Issue Type: Improvement
>> Reporter: Jukka Zitting
>> Assigned To: Norman Maurer
>> Attachments: MimeException.patch
>>
>>
>> There is currently no good way for a Mime4j ContentHandler to indicate that it has failed to process a message event and that no further events should be generated. Compare this with for example the SAX ContentHandler interface that allows implementing classes to throw SAXExceptions.
>> Being able to throw such processing exceptions is important for example for a handler that wants to incrementally store a message in a backend store like a relational database or a JCR content repository.
>> My proposal is to add a new MimeException exception class and allow it to be thrown from any of the ContentHandler methods. Such a change would be incompatible with any parser and other classes that call the ContentHandler methods (even indirectly, for example through the MimeStreamParser class), but existing classes that implement the ContentHandler interface would not be affected.
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Commented: (MIME4J-16) Allow exceptions from a
ContentHandler
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/MIME4J-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496804 ]
Norman Maurer commented on MIME4J-16:
-------------------------------------
I like the idea... The question is should we apply the patch before tagging the svn for 0.3 release or after ?
> Allow exceptions from a ContentHandler
> --------------------------------------
>
> Key: MIME4J-16
> URL: https://issues.apache.org/jira/browse/MIME4J-16
> Project: Mime4j
> Issue Type: Improvement
> Reporter: Jukka Zitting
> Assigned To: Norman Maurer
> Attachments: MimeException.patch
>
>
> There is currently no good way for a Mime4j ContentHandler to indicate that it has failed to process a message event and that no further events should be generated. Compare this with for example the SAX ContentHandler interface that allows implementing classes to throw SAXExceptions.
> Being able to throw such processing exceptions is important for example for a handler that wants to incrementally store a message in a backend store like a relational database or a JCR content repository.
> My proposal is to add a new MimeException exception class and allow it to be thrown from any of the ContentHandler methods. Such a change would be incompatible with any parser and other classes that call the ContentHandler methods (even indirectly, for example through the MimeStreamParser class), but existing classes that implement the ContentHandler interface would not be affected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Commented: (MIME4J-16) Allow exceptions from a
ContentHandler
Posted by "Jukka Zitting (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/MIME4J-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499077 ]
Jukka Zitting commented on MIME4J-16:
-------------------------------------
Hmm, I seem to have forgotten to select the "grant license" option on the attachment upload screen. For the record, both versions of the patch are meant for inclusion under the Apache License.
> Allow exceptions from a ContentHandler
> --------------------------------------
>
> Key: MIME4J-16
> URL: https://issues.apache.org/jira/browse/MIME4J-16
> Project: Mime4j
> Issue Type: Improvement
> Reporter: Jukka Zitting
> Assigned To: Norman Maurer
> Fix For: 0.4
>
> Attachments: MimeException.patch, MimeException.patch
>
>
> There is currently no good way for a Mime4j ContentHandler to indicate that it has failed to process a message event and that no further events should be generated. Compare this with for example the SAX ContentHandler interface that allows implementing classes to throw SAXExceptions.
> Being able to throw such processing exceptions is important for example for a handler that wants to incrementally store a message in a backend store like a relational database or a JCR content repository.
> My proposal is to add a new MimeException exception class and allow it to be thrown from any of the ContentHandler methods. Such a change would be incompatible with any parser and other classes that call the ContentHandler methods (even indirectly, for example through the MimeStreamParser class), but existing classes that implement the ContentHandler interface would not be affected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Updated: (MIME4J-16) Allow exceptions from a ContentHandler
Posted by "Jukka Zitting (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/MIME4J-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated MIME4J-16:
--------------------------------
Fix Version/s: 0.4
Sounds reasonable. Tagged this for 0.4
> Allow exceptions from a ContentHandler
> --------------------------------------
>
> Key: MIME4J-16
> URL: https://issues.apache.org/jira/browse/MIME4J-16
> Project: Mime4j
> Issue Type: Improvement
> Reporter: Jukka Zitting
> Assigned To: Norman Maurer
> Fix For: 0.4
>
> Attachments: MimeException.patch
>
>
> There is currently no good way for a Mime4j ContentHandler to indicate that it has failed to process a message event and that no further events should be generated. Compare this with for example the SAX ContentHandler interface that allows implementing classes to throw SAXExceptions.
> Being able to throw such processing exceptions is important for example for a handler that wants to incrementally store a message in a backend store like a relational database or a JCR content repository.
> My proposal is to add a new MimeException exception class and allow it to be thrown from any of the ContentHandler methods. Such a change would be incompatible with any parser and other classes that call the ContentHandler methods (even indirectly, for example through the MimeStreamParser class), but existing classes that implement the ContentHandler interface would not be affected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Updated: (MIME4J-16) Allow exceptions from a ContentHandler
Posted by "Jukka Zitting (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/MIME4J-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated MIME4J-16:
--------------------------------
Attachment: MimeException.patch
Attached a patch (MimeException.patch) that implements the proposed change.
> Allow exceptions from a ContentHandler
> --------------------------------------
>
> Key: MIME4J-16
> URL: https://issues.apache.org/jira/browse/MIME4J-16
> Project: Mime4j
> Issue Type: Improvement
> Reporter: Jukka Zitting
> Attachments: MimeException.patch
>
>
> There is currently no good way for a Mime4j ContentHandler to indicate that it has failed to process a message event and that no further events should be generated. Compare this with for example the SAX ContentHandler interface that allows implementing classes to throw SAXExceptions.
> Being able to throw such processing exceptions is important for example for a handler that wants to incrementally store a message in a backend store like a relational database or a JCR content repository.
> My proposal is to add a new MimeException exception class and allow it to be thrown from any of the ContentHandler methods. Such a change would be incompatible with any parser and other classes that call the ContentHandler methods (even indirectly, for example through the MimeStreamParser class), but existing classes that implement the ContentHandler interface would not be affected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Commented: (MIME4J-16) Allow exceptions from a
ContentHandler
Posted by "Jukka Zitting (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/MIME4J-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496919 ]
Jukka Zitting commented on MIME4J-16:
-------------------------------------
It's a relatively major API change, so if there's consensus on doing this it makes sense to have it included in an 0.x release as early as possible to avoid compatibility issues later on. But if the 0.3 release is already ready to go, then it might be easier to wait for the next release.
> Allow exceptions from a ContentHandler
> --------------------------------------
>
> Key: MIME4J-16
> URL: https://issues.apache.org/jira/browse/MIME4J-16
> Project: Mime4j
> Issue Type: Improvement
> Reporter: Jukka Zitting
> Assigned To: Norman Maurer
> Attachments: MimeException.patch
>
>
> There is currently no good way for a Mime4j ContentHandler to indicate that it has failed to process a message event and that no further events should be generated. Compare this with for example the SAX ContentHandler interface that allows implementing classes to throw SAXExceptions.
> Being able to throw such processing exceptions is important for example for a handler that wants to incrementally store a message in a backend store like a relational database or a JCR content repository.
> My proposal is to add a new MimeException exception class and allow it to be thrown from any of the ContentHandler methods. Such a change would be incompatible with any parser and other classes that call the ContentHandler methods (even indirectly, for example through the MimeStreamParser class), but existing classes that implement the ContentHandler interface would not be affected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Commented: (MIME4J-16) Allow exceptions from a
ContentHandler
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/MIME4J-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497138 ]
Norman Maurer commented on MIME4J-16:
-------------------------------------
Well the 0.3 release was tested long time and only waiting for the VOTE. So I think its safer to release 0.3 first and after that apply the patch to not get bad suprises
> Allow exceptions from a ContentHandler
> --------------------------------------
>
> Key: MIME4J-16
> URL: https://issues.apache.org/jira/browse/MIME4J-16
> Project: Mime4j
> Issue Type: Improvement
> Reporter: Jukka Zitting
> Assigned To: Norman Maurer
> Attachments: MimeException.patch
>
>
> There is currently no good way for a Mime4j ContentHandler to indicate that it has failed to process a message event and that no further events should be generated. Compare this with for example the SAX ContentHandler interface that allows implementing classes to throw SAXExceptions.
> Being able to throw such processing exceptions is important for example for a handler that wants to incrementally store a message in a backend store like a relational database or a JCR content repository.
> My proposal is to add a new MimeException exception class and allow it to be thrown from any of the ContentHandler methods. Such a change would be incompatible with any parser and other classes that call the ContentHandler methods (even indirectly, for example through the MimeStreamParser class), but existing classes that implement the ContentHandler interface would not be affected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Resolved: (MIME4J-16) Allow exceptions from a ContentHandler
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/MIME4J-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Norman Maurer resolved MIME4J-16.
---------------------------------
Resolution: Fixed
Patch applied! thx
> Allow exceptions from a ContentHandler
> --------------------------------------
>
> Key: MIME4J-16
> URL: https://issues.apache.org/jira/browse/MIME4J-16
> Project: Mime4j
> Issue Type: Improvement
> Reporter: Jukka Zitting
> Assigned To: Norman Maurer
> Fix For: 0.4
>
> Attachments: MimeException.patch, MimeException.patch
>
>
> There is currently no good way for a Mime4j ContentHandler to indicate that it has failed to process a message event and that no further events should be generated. Compare this with for example the SAX ContentHandler interface that allows implementing classes to throw SAXExceptions.
> Being able to throw such processing exceptions is important for example for a handler that wants to incrementally store a message in a backend store like a relational database or a JCR content repository.
> My proposal is to add a new MimeException exception class and allow it to be thrown from any of the ContentHandler methods. Such a change would be incompatible with any parser and other classes that call the ContentHandler methods (even indirectly, for example through the MimeStreamParser class), but existing classes that implement the ContentHandler interface would not be affected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Assigned: (MIME4J-16) Allow exceptions from a ContentHandler
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/MIME4J-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Norman Maurer reassigned MIME4J-16:
-----------------------------------
Assignee: Norman Maurer
> Allow exceptions from a ContentHandler
> --------------------------------------
>
> Key: MIME4J-16
> URL: https://issues.apache.org/jira/browse/MIME4J-16
> Project: Mime4j
> Issue Type: Improvement
> Reporter: Jukka Zitting
> Assigned To: Norman Maurer
> Attachments: MimeException.patch
>
>
> There is currently no good way for a Mime4j ContentHandler to indicate that it has failed to process a message event and that no further events should be generated. Compare this with for example the SAX ContentHandler interface that allows implementing classes to throw SAXExceptions.
> Being able to throw such processing exceptions is important for example for a handler that wants to incrementally store a message in a backend store like a relational database or a JCR content repository.
> My proposal is to add a new MimeException exception class and allow it to be thrown from any of the ContentHandler methods. Such a change would be incompatible with any parser and other classes that call the ContentHandler methods (even indirectly, for example through the MimeStreamParser class), but existing classes that implement the ContentHandler interface would not be affected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org