[jira] Closed: (JAMES-96) Mailet container should not trap exceptions in init()

[ji...@apache.org]

Message:

   The following issue has been closed.

   Resolver: Noel J. Bergman
       Date: Tue, 13 Apr 2004 12:54 PM

Didn't understand the initial complaint until re-reading.  Found the problem, which has to do with the nested exception not being rendered.  There is a fix in CVS that handles one level of nesting.  A better solution would be good, but this should handle most cases.
---------------------------------------------------------------------
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: Closed
   Priority: Minor
 Resolution: FIXED

    Project: James
 Components: 
             SpoolManager & Processors
   Fix Fors:
             2.2.0a19
   Versions:
             1.2.1

   Assignee: 
   Reporter: benengber

    Created: Tue, 18 Mar 2003 8:47 PM
    Updated: Tue, 13 Apr 2004 12:54 PM
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