You are viewing a plain text version of this content. The canonical link for it is here.

Posted to pluto-dev@portals.apache.org by "Craig Doremus (JIRA)" <pl...@jakarta.apache.org> on 2005/07/08 16:28:10 UTC

[jira] Resolved: (PLUTO-136) Exceptions in Deploy class not propagated to the Admin portlets

     [ http://issues.apache.org/jira/browse/PLUTO-136?page=all ]
     
Craig Doremus resolved PLUTO-136:
---------------------------------

    Resolution: Fixed

Fixed in revision 209783 of org.apache.pluto.portalImpl.Deploy in Subversion.

> Exceptions in Deploy class not propagated to the Admin portlets
> ---------------------------------------------------------------
>
>          Key: PLUTO-136
>          URL: http://issues.apache.org/jira/browse/PLUTO-136
>      Project: Pluto
>         Type: Bug
>   Components: deployer, portal driver
>     Versions: 1.0.1-rc3
>  Environment: All
>     Reporter: Craig Doremus
>     Assignee: Craig Doremus
>      Fix For: Current CVS

>
> The Admin portlet application uses the org.apache.pluto.portalImpl.Deploy class to deploy a custom portlet, calling its main() method. However, main() catches and eats all Exceptions except for printing a stack trace to standard output. These Exceptions need to be rethrown and dealt with by the DeployWarPortlet in the Admin portlet app.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira