[
https://issues.apache.org/struts/browse/STR-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42385
]
Ralf Hauser commented on STR-3105:
----------------------------------
Thanks for all the comments, if I understand what I find on your site
correctly. the suggested minimum is to use Struts-EL since it appears to give
the flexibility to gradually move towards JSTL.
in the menu on the left side on the web-page http://struts.apache.org/1.3.9/,
I'd still add a style element as such:
<li class="none">
<a href="http://struts.apache.org/1.3.9/struts-taglib/index.html";
style="font-style:italic;text-decoration: line-through;" >Struts
Taglib</a>
</li>
> 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.
