You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Paul Benedict (JIRA)" <ji...@apache.org> on 2007/10/12 03:04:38 UTC
[jira] Updated: (STR-3105) Document how to migrate tags to
JSTL
[ https://issues.apache.org/struts/browse/STR-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Benedict updated STR-3105:
-------------------------------
Component/s: (was: Taglibs)
Website
Priority: Minor (was: Major)
Issue Type: Improvement (was: New Feature)
Summary: Document how to migrate <logic> tags to JSTL (was: add an optional <logic:else> tag)
> Document how to migrate <logic> tags to JSTL
> --------------------------------------------
>
> Key: STR-3105
> URL: https://issues.apache.org/struts/browse/STR-3105
> Project: Struts 1
> Issue Type: Improvement
> Components: Website
> Affects Versions: 1.3.8
> Environment: any
> Reporter: Ralf Hauser
> Priority: Minor
>
> 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.