struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lukasz Lenart (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (WW-4137) Parameter warnings being generated in logs after 2.3.7 in portlet
Date Tue, 30 Jul 2013 19:23:49 GMT

    [ https://issues.apache.org/jira/browse/WW-4137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13724287#comment-13724287
] 

Lukasz Lenart edited comment on WW-4137 at 7/30/13 7:22 PM:
------------------------------------------------------------

[~spudwebs] you can blame me :\ And to clarify why the original Version Notes was updated
is because we cannot change what was signed as a release :/
                
      was (Author: lukaszlenart):
    [~spudwebs] you can blame me :\
                  
> Parameter warnings being generated in logs after 2.3.7 in portlet
> -----------------------------------------------------------------
>
>                 Key: WW-4137
>                 URL: https://issues.apache.org/jira/browse/WW-4137
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Plugin - Portlet
>    Affects Versions: 2.3.7, 2.3.8, 2.3.12, 2.3.14, 2.3.14.1, 2.3.14.2, 2.3.14.3, 2.3.15
>         Environment: liferay portal running in tomcat
>            Reporter: Shawn Andrews
>            Assignee: Bruce Phillips
>            Priority: Minor
>             Fix For: 2.3.16
>
>
> I tried to migrate some portlets from 2.3.4  to 2.3.7 (actually to 2.3.15 but have found
that the problem starts in 2.3.7)
> What happens is there is now a warning in the logs whenever I execute an action.
> 09:33:35,327 WARN  [OgnlValueStack:60] Error setting expression 'struts.portlet.action'
with value '[Ljava.lang.String;@78f28bba'
> ognl.OgnlException: source is null for getProperty(null, "portlet")
> It seems that in older versions of struts portlet plugin this parameter use to be taken
out,  since I believe it is used by struts2 to know what action to execute, but should maybe
not be stored in the OGNL stack.   My guess is that this has to do with no field called 'portlet'
 with property 'action' in my action class existing to place the expression.
> In version 2.3.4.1 and previous this was not an issue. Maybe the portlet interceptor
was taking this parameters out before it was placed into OGNL, and now it is being left?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message