[
https://issues.apache.org/struts/browse/STR-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42371
]
Niall Pemberton commented on STR-3105:
--------------------------------------
I wrote if/then/else and switch/case tags (based on the Struts logic tags) back
in 2001 [1] - but the opinion[2] then was that we should encourage users to use
the JSTL and not continue to add logic tags to Struts. IMO there was possibly a
case to add this kind of stuff back in 2001 since JSTL was only on the horizon
- but having lost that argument then, then theres less reason to reverse it now
where I doubt anyone uses a servlet container that doesn't support JSTL.
[1] http://husted.com/struts/resources/logic-niallp.htm
[2] http://tinyurl.com/2x99gd
> add an optional <logic:else> tag
> --------------------------------
>
> Key: STR-3105
> URL: https://issues.apache.org/struts/browse/STR-3105
> Project: Struts 1
> Issue Type: New Feature
> Components: Taglibs
> Affects Versions: 1.3.8
> Environment: any
> Reporter: Ralf Hauser
>
> Very often, I find myself having a
> <logic:equal .... true
> .... positive
> </logic:equal
> followed by a
> <logic:notEqual .... true
> .... negative
> </logic:notEqual
> These are maintenance imponderables because in nested settings, you risk to
> loose oversight if you change one of the statements to also change the other
> one.
> If there were a <logic:else>
> the above statement could be reduced to
> <logic:equal .... true>
> .... positive ...
> </logic:else>
> .... negative ...
> </logic:equal>
> and only ONE condition is to be maintained
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
