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 ji...@apache.org on 2004/04/13 20:30:43 UTC
[jira] Updated: (JAMES-96) Mailet container should not trap exceptions in init()
The following issue has been updated:
Updater: Noel J. Bergman (mailto:noel@devtech.com)
Date: Tue, 13 Apr 2004 11:29 AM
Changes:
assignee changed from James Developers Mailing List
description changed from If a custom mailet throws a RuntimeException in init(), the container traps it and rethrows
a MessagingException, giving little indication of what occurred. The container really
ought to provide the stack trace of the failure. to If a custom mailet throws a RuntimeException in init(), the container traps it and rethrows
a MessagingException, giving little indication of what occurred. The container really
ought to provide the stack trace of the failure.
environment changed from Operating System: All
Platform: All to Operating System: All
Platform: All
priority changed to Minor
Component changed to SpoolManager & Processors
Component changed from Mailet API
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-96?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JAMES-96
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JAMES-96
Summary: Mailet container should not trap exceptions in init()
Type: Bug
Status: Unassigned
Priority: Minor
Project: James
Components:
SpoolManager & Processors
Versions:
1.2.1
Assignee:
Reporter: benengber
Created: Tue, 18 Mar 2003 8:47 PM
Updated: Tue, 13 Apr 2004 11:29 AM
Environment: Operating System: All
Platform: All
Description:
If a custom mailet throws a RuntimeException in init(), the container traps it and rethrows
a MessagingException, giving little indication of what occurred. The container really
ought to provide the stack trace of the failure.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org