You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org> on 2005/05/11 18:13:13 UTC
[jira] Created: (TAPESTRY-323) Option for Strict vs. Default ErrorHandler
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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Assigned: (TAPESTRY-323) Option for Strict vs. Default ErrorHandler
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Closed: (TAPESTRY-323) Option for Strict vs. Default ErrorHandler
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Commented: (TAPESTRY-323) Option for Strict vs. Default ErrorHandler
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org