[jira] Created: (TAPESTRY-323) Option for Strict vs. Default ErrorHandler

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (TAPESTRY-323) Option for Strict vs. Default ErrorHandler

JIRA tapestry-dev@jakarta.apache.org
Option for Strict vs. Default ErrorHandler
------------------------------------------

         Key: TAPESTRY-323
         URL: http://issues.apache.org/jira/browse/TAPESTRY-323
     Project: Tapestry
        Type: New Feature
  Components: Framework  
    Versions: 4.0    
    Reporter: Howard M. Lewis Ship
     Fix For: 4.0


When ApplicationServlet builds the Registry, it always uses the DefaultErrorHandler.

Would be nice if this was configurable, i.e., a servlet initializataion parameter org.apache.tapestry.strict-error-handling=true, to
 use the StrictErrorHandlerimplementation rather than the DefaultErrorHandler implementation.

However, Erik feels that we should simply default to StrictErrorHandler, and he may be right.  But we still want a way to control this, especially to allow other implementations of ErrorHandler.

--
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


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] Assigned: (TAPESTRY-323) Option for Strict vs. Default ErrorHandler

JIRA tapestry-dev@jakarta.apache.org
     [ http://issues.apache.org/jira/browse/TAPESTRY-323?page=all ]

Howard M. Lewis Ship reassigned TAPESTRY-323:
---------------------------------------------

    Assign To: Howard M. Lewis Ship

> Option for Strict vs. Default ErrorHandler
> ------------------------------------------
>
>          Key: TAPESTRY-323
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-323
>      Project: Tapestry
>         Type: New Feature
>   Components: Framework
>     Versions: 4.0
>     Reporter: Howard M. Lewis Ship
>     Assignee: Howard M. Lewis Ship
>      Fix For: 4.0

>
> When ApplicationServlet builds the Registry, it always uses the DefaultErrorHandler.
> Would be nice if this was configurable, i.e., a servlet initializataion parameter org.apache.tapestry.strict-error-handling=true, to
>  use the StrictErrorHandlerimplementation rather than the DefaultErrorHandler implementation.
> However, Erik feels that we should simply default to StrictErrorHandler, and he may be right.  But we still want a way to control this, especially to allow other implementations of ErrorHandler.

--
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


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (TAPESTRY-323) Option for Strict vs. Default ErrorHandler

JIRA tapestry-dev@jakarta.apache.org
In reply to this post by JIRA tapestry-dev@jakarta.apache.org
     [ http://issues.apache.org/jira/browse/TAPESTRY-323?page=comments#action_65022 ]
     
Howard M. Lewis Ship commented on TAPESTRY-323:
-----------------------------------------------

First pass will be to provide a protected method that can be overriden.  Also, changing to use StringErrorHandler by default (rather than the lenient DefaultErrorHandler).

> Option for Strict vs. Default ErrorHandler
> ------------------------------------------
>
>          Key: TAPESTRY-323
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-323
>      Project: Tapestry
>         Type: New Feature
>   Components: Framework
>     Versions: 4.0
>     Reporter: Howard M. Lewis Ship
>     Assignee: Howard M. Lewis Ship
>      Fix For: 4.0

>
> When ApplicationServlet builds the Registry, it always uses the DefaultErrorHandler.
> Would be nice if this was configurable, i.e., a servlet initializataion parameter org.apache.tapestry.strict-error-handling=true, to
>  use the StrictErrorHandlerimplementation rather than the DefaultErrorHandler implementation.
> However, Erik feels that we should simply default to StrictErrorHandler, and he may be right.  But we still want a way to control this, especially to allow other implementations of ErrorHandler.

--
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


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] Closed: (TAPESTRY-323) Option for Strict vs. Default ErrorHandler

JIRA tapestry-dev@jakarta.apache.org
In reply to this post by JIRA tapestry-dev@jakarta.apache.org
     [ http://issues.apache.org/jira/browse/TAPESTRY-323?page=all ]
     
Howard M. Lewis Ship closed TAPESTRY-323:
-----------------------------------------

    Resolution: Fixed

> Option for Strict vs. Default ErrorHandler
> ------------------------------------------
>
>          Key: TAPESTRY-323
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-323
>      Project: Tapestry
>         Type: New Feature
>   Components: Framework
>     Versions: 4.0
>     Reporter: Howard M. Lewis Ship
>     Assignee: Howard M. Lewis Ship
>      Fix For: 4.0

>
> When ApplicationServlet builds the Registry, it always uses the DefaultErrorHandler.
> Would be nice if this was configurable, i.e., a servlet initializataion parameter org.apache.tapestry.strict-error-handling=true, to
>  use the StrictErrorHandlerimplementation rather than the DefaultErrorHandler implementation.
> However, Erik feels that we should simply default to StrictErrorHandler, and he may be right.  But we still want a way to control this, especially to allow other implementations of ErrorHandler.

--
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


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]