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 "Eric Dalquist (JIRA)" <ji...@apache.org> on 2008/01/02 20:02:33 UTC

[jira] Created: (PLUTO-457) PortletContainerException doesn't chain Throwable

PortletContainerException doesn't chain Throwable
-------------------------------------------------

                 Key: PLUTO-457
                 URL: https://issues.apache.org/jira/browse/PLUTO-457
             Project: Pluto
          Issue Type: Bug
          Components: general
    Affects Versions: 1.1.4
            Reporter: Eric Dalquist
             Fix For: 1.1.5


The constructors for PortletContainerException that take a Throwable as an argument fail to pass it to the parent Exception resulting in the root cause stack trace getting lost in log messages.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (PLUTO-457) PortletContainerException doesn't chain Throwable

Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555946#action_12555946 ] 

Craig Doremus commented on PLUTO-457:
-------------------------------------

Applied patch to pluto-1.1.x branch in SVN version 608889.

> PortletContainerException doesn't chain Throwable
> -------------------------------------------------
>
>                 Key: PLUTO-457
>                 URL: https://issues.apache.org/jira/browse/PLUTO-457
>             Project: Pluto
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 1.1.4
>            Reporter: Eric Dalquist
>             Fix For: 1.1.5, 1.1-286-trunk-merge
>
>         Attachments: PortletContainerException.patch
>
>
> The constructors for PortletContainerException that take a Throwable as an argument fail to pass it to the parent Exception resulting in the root cause stack trace getting lost in log messages.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (PLUTO-457) PortletContainerException doesn't chain Throwable

Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555949#action_12555949 ] 

Craig Doremus commented on PLUTO-457:
-------------------------------------

Applied patch to trunk in SVN rev 608891.

> PortletContainerException doesn't chain Throwable
> -------------------------------------------------
>
>                 Key: PLUTO-457
>                 URL: https://issues.apache.org/jira/browse/PLUTO-457
>             Project: Pluto
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 1.1.4
>            Reporter: Eric Dalquist
>             Fix For: 1.2.0, 1.1.5, 1.1-286-trunk-merge
>
>         Attachments: PortletContainerException.patch
>
>
> The constructors for PortletContainerException that take a Throwable as an argument fail to pass it to the parent Exception resulting in the root cause stack trace getting lost in log messages.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (PLUTO-457) PortletContainerException doesn't chain Throwable

Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PLUTO-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Craig Doremus updated PLUTO-457:
--------------------------------

    Fix Version/s: 1.1-286-trunk-merge

Added 1.1-286-trunk-merge as a fix version

> PortletContainerException doesn't chain Throwable
> -------------------------------------------------
>
>                 Key: PLUTO-457
>                 URL: https://issues.apache.org/jira/browse/PLUTO-457
>             Project: Pluto
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 1.1.4
>            Reporter: Eric Dalquist
>             Fix For: 1.1.5, 1.1-286-trunk-merge
>
>         Attachments: PortletContainerException.patch
>
>
> The constructors for PortletContainerException that take a Throwable as an argument fail to pass it to the parent Exception resulting in the root cause stack trace getting lost in log messages.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (PLUTO-457) PortletContainerException doesn't chain Throwable

Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PLUTO-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Craig Doremus resolved PLUTO-457.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2.0

Patches applied to trunk and all relevant branches.

> PortletContainerException doesn't chain Throwable
> -------------------------------------------------
>
>                 Key: PLUTO-457
>                 URL: https://issues.apache.org/jira/browse/PLUTO-457
>             Project: Pluto
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 1.1.4
>            Reporter: Eric Dalquist
>             Fix For: 1.2.0, 1.1.5, 1.1-286-trunk-merge
>
>         Attachments: PortletContainerException.patch
>
>
> The constructors for PortletContainerException that take a Throwable as an argument fail to pass it to the parent Exception resulting in the root cause stack trace getting lost in log messages.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (PLUTO-457) PortletContainerException doesn't chain Throwable

Posted by "Eric Dalquist (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PLUTO-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Dalquist updated PLUTO-457:
--------------------------------

    Attachment: PortletContainerException.patch

Patch to chain the exceptions

> PortletContainerException doesn't chain Throwable
> -------------------------------------------------
>
>                 Key: PLUTO-457
>                 URL: https://issues.apache.org/jira/browse/PLUTO-457
>             Project: Pluto
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 1.1.4
>            Reporter: Eric Dalquist
>             Fix For: 1.1.5
>
>         Attachments: PortletContainerException.patch
>
>
> The constructors for PortletContainerException that take a Throwable as an argument fail to pass it to the parent Exception resulting in the root cause stack trace getting lost in log messages.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (PLUTO-457) PortletContainerException doesn't chain Throwable

Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PLUTO-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555791#action_12555791 ] 

Craig Doremus commented on PLUTO-457:
-------------------------------------

Applied patch to 1.1-286-trunk-merge in SVN rev 608742. Thanks Eric!

> PortletContainerException doesn't chain Throwable
> -------------------------------------------------
>
>                 Key: PLUTO-457
>                 URL: https://issues.apache.org/jira/browse/PLUTO-457
>             Project: Pluto
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 1.1.4
>            Reporter: Eric Dalquist
>             Fix For: 1.1.5
>
>         Attachments: PortletContainerException.patch
>
>
> The constructors for PortletContainerException that take a Throwable as an argument fail to pass it to the parent Exception resulting in the root cause stack trace getting lost in log messages.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.