You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2010/05/18 20:40:42 UTC

[jira] Created: (TAP5-1157) Client-side exceptions during Tapestry.init() should be caught and reported with the console

Client-side exceptions during Tapestry.init() should be caught and reported with the console
--------------------------------------------------------------------------------------------

                 Key: TAP5-1157
                 URL: https://issues.apache.org/jira/browse/TAP5-1157
             Project: Tapestry 5
          Issue Type: Improvement
          Components: tapestry-core
    Affects Versions: 5.2.0
            Reporter: Howard M. Lewis Ship
            Priority: Minor


Currently, the entire call to Tapestry.init() will blow up. It would be best to report the error to the console and continue as best as possible. As currently coded, it can be very hard to track down what actually failed.

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


[jira] Closed: (TAP5-1157) Client-side exceptions during Tapestry.init() should be caught and reported with the console

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-1157.
--------------------------------------

    Fix Version/s: 5.2.0
       Resolution: Fixed

> Client-side exceptions during Tapestry.init() should be caught and reported with the console
> --------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1157
>                 URL: https://issues.apache.org/jira/browse/TAP5-1157
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.2.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>             Fix For: 5.2.0
>
>
> Currently, the entire call to Tapestry.init() will blow up. It would be best to report the error to the console and continue as best as possible. As currently coded, it can be very hard to track down what actually failed.

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


[jira] Closed: (TAP5-1157) Client-side exceptions during Tapestry.init() should be caught and reported with the console

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-1157.
--------------------------------------

    Fix Version/s: 5.2.0
       Resolution: Fixed

> Client-side exceptions during Tapestry.init() should be caught and reported with the console
> --------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1157
>                 URL: https://issues.apache.org/jira/browse/TAP5-1157
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.2.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>             Fix For: 5.2.0
>
>
> Currently, the entire call to Tapestry.init() will blow up. It would be best to report the error to the console and continue as best as possible. As currently coded, it can be very hard to track down what actually failed.

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


[jira] Assigned: (TAP5-1157) Client-side exceptions during Tapestry.init() should be caught and reported with the console

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship reassigned TAP5-1157:
------------------------------------------

    Assignee: Howard M. Lewis Ship

> Client-side exceptions during Tapestry.init() should be caught and reported with the console
> --------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1157
>                 URL: https://issues.apache.org/jira/browse/TAP5-1157
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.2.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>
> Currently, the entire call to Tapestry.init() will blow up. It would be best to report the error to the console and continue as best as possible. As currently coded, it can be very hard to track down what actually failed.

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


[jira] Assigned: (TAP5-1157) Client-side exceptions during Tapestry.init() should be caught and reported with the console

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship reassigned TAP5-1157:
------------------------------------------

    Assignee: Howard M. Lewis Ship

> Client-side exceptions during Tapestry.init() should be caught and reported with the console
> --------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1157
>                 URL: https://issues.apache.org/jira/browse/TAP5-1157
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.2.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>
> Currently, the entire call to Tapestry.init() will blow up. It would be best to report the error to the console and continue as best as possible. As currently coded, it can be very hard to track down what actually failed.

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