You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "John Lindal (JIRA)" <ji...@apache.org> on 2011/01/31 21:10:32 UTC
[jira] Resolved: (WW-3546) Add ability to control devMode per
request
[ https://issues.apache.org/jira/browse/WW-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Lindal resolved WW-3546.
-----------------------------
Resolution: Fixed
> Add ability to control devMode per request
> ------------------------------------------
>
> Key: WW-3546
> URL: https://issues.apache.org/jira/browse/WW-3546
> Project: Struts 2
> Issue Type: New Feature
> Components: Core Interceptors, Dispatch Filter, Plugin - JSON
> Affects Versions: 2.2.1
> Reporter: John Lindal
> Assignee: John Lindal
> Priority: Minor
> Fix For: 2.2.2
>
>
> I have found it useful to be able to control "debugging mode" on a per-request basis. It makes it easier to track down problems reported in production that are hard to reproduce in a development environment.
> The places that I have found where it would be useful to control devMode are: Dispatcher.sendError(), JSONInterceptor, and DebuggingInterceptor. (Other uses of devMode are related to logging and config reloading, and that shouldn't be adjustable.)
> I've currently patched my copy of Struts 2.2.1 so each of the the above-mentioned code chunks checks an extra, static ThreadLocal variable that I added (in addition to the devMode member variable).
> 1) Is this the best solution?
> 2) Is this something that should be merged into the Struts 2 distribution?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira