You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Maurizio Cucchiara (JIRA)" <ji...@apache.org> on 2011/06/04 17:06:47 UTC

[jira] [Closed] (WW-3585) Struts2 debugging using debug=browser in url does not populate url parameters in action class member variables

     [ https://issues.apache.org/jira/browse/WW-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maurizio Cucchiara closed WW-3585.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.3

Moved the debug interceptor to the bottom of the stack

> Struts2 debugging using debug=browser in url does not populate url parameters in action class member variables
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: WW-3585
>                 URL: https://issues.apache.org/jira/browse/WW-3585
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Core Interceptors
>    Affects Versions: 2.2.1, 2.2.1.1
>         Environment: Windows 7 Struts2.2.1 basic jars found in blank.war plus code convention/annotation jar and struts2-config-browser-plugin-2.2.1.jar
>            Reporter: samarjit samanta
>            Assignee: Maurizio Cucchiara
>            Priority: Minor
>             Fix For: 2.3
>
>
> When pass a few variables in url and pupulate the same in action class and System.out.print() those variables, I can see them getting populated and prints tomcat  console. But the same action class when debugging using browser `debug=browser` the action class variables are null or remain in initialized value and 'null' gets printed on tomcat console corresponding to that variable. The variable gets displayed in #parameters.
>  However, the other two debugging technique like `debug=console` shows the values in action which is normal. Also `debug=xml` also shows the value in action and in tomcat console also it is printed properly.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira