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

Aleksandr Mashchenko commented on WW-5004:
------------------------------------------

We've discovered same bug today. It is broken by this commit 
[https://github.com/jkuhnert/ognl/commit/4da6759b2f8e746cd1b8fbfabde5d067e3ea0baa]
 in OGNL.

NPE is thrown somewhere in {{ProxyUtil}} and even if it is fixed then 
displaying static field still doesn't work.

I wonder why do we need to call MemberAccess in case of static fields at all?

Also why do OGNL allows to access private static fields? It doesn't seem 
reasonable.

 

> No more calling of a static variable in Struts 2.8.20 available
> ---------------------------------------------------------------
>
>                 Key: WW-5004
>                 URL: https://issues.apache.org/jira/browse/WW-5004
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.5.20
>         Environment: Java 7.1 and JSP Websites
>            Reporter: Deniz Renkligül
>            Priority: Critical
>              Labels: build, features, patch, usability
>             Fix For: 2.5.21, 2.6
>
>
> After the update from Struts 2.5.18 to 2.5.20 it is not more possible to call 
> a java static variable in JSP like
> {code:java}
> <s:property value="@my.package.folder.my.staticClass@myStaticThemeVersion" />
> {code}
> Please see for more details the release notes of 2.5.20
>  [link 
> https://cwiki.apache.org/confluence/display/WW/Version+Notes+2.5.20|https://cwiki.apache.org/confluence/display/WW/Version+Notes+2.5.20]
>  and I tried without success the following description assigned above in the 
> release version notes 2.5.20 with :
> {code:java}
> <constant name="struts.configuration.xml.reload" value="false"/>
> <constant name="struts.serve.static" value="true" />
> {code}
>  https://issues.apache.org/jira/browse/WW-4984
>  
> Thanks in advance for your support.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to