struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nikos dimitrakas (Jira)" <>
Subject [jira] [Created] (WW-5093) inconsistent scope for variables created with s:set and s:url
Date Thu, 08 Oct 2020 20:42:00 GMT
nikos dimitrakas created WW-5093:

             Summary: inconsistent scope for variables created with s:set and s:url
                 Key: WW-5093
             Project: Struts 2
          Issue Type: Bug
          Components: Core Tags
    Affects Versions: 2.5.22
            Reporter: nikos dimitrakas

The implementation of s:set and s:url and s:text is not consistent and not well documented. 

Creating a variable with s:set puts the variable in a different default scope than creating
a variable with s:url or s:text (with the attribute var). It is also not documented what the
default scope is. After testing I could conclude that the scope for a variable created by
s:url is request, while the default of s:set is not. Furthermore, s:set offers a possibility
to specify the scope with an attribute, But s:url and s:text do not. 

Possible options would be offering the possibility to specify the scope attribute in s:url
and s:text, or dropping support for the var attribute for s:url and s:text and only allow
s:set to create variables (thus being forced to nest s:url and s:text inside an s:set). That
would be symmetric with how s:property does not offer the var attribute. At minimum all three
tags should have the same default and their default should be explicitly specified in the
documentation (in the tld and the online manual / tag reference)

This message was sent by Atlassian Jira

View raw message