You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Henri Yandell (JIRA)" <ji...@apache.org> on 2007/06/13 06:50:26 UTC
[jira] Created: (STR-3055) Figure out the 'disabled="${!empty
pageScope}" in EL-Example
Figure out the 'disabled="${!empty pageScope}" in EL-Example
------------------------------------------------------------
Key: STR-3055
URL: https://issues.apache.org/struts/browse/STR-3055
Project: Struts 1
Issue Type: Task
Components: Apps
Affects Versions: 1.3.9
Reporter: Henri Yandell
Assignee: Henri Yandell
Priority: Minor
Fix For: 1.3.10, 1.4.0
The EL-Example has lots of 'disabled="${!empty pageScope}". This seems hugely confusing - why say that and not just 'true' or 'false'.
At the minimum, need to explain when it's happening so people know a field is meant to be disabled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (STR-3055) Figure out the 'disabled="${!empty
pageScope}" in EL-Example
Posted by "Paul Benedict (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/STR-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Benedict resolved STR-3055.
--------------------------------
Resolution: Not A Problem
After playing around with the app, it became obvious that the cryptic "!empty pageScope" is a way of demonstrating EL. Yes, a verbose way of getting true or false, but a sure way of generating those values through an example.
> Figure out the 'disabled="${!empty pageScope}" in EL-Example
> ------------------------------------------------------------
>
> Key: STR-3055
> URL: https://issues.apache.org/struts/browse/STR-3055
> Project: Struts 1
> Issue Type: Task
> Components: Apps
> Affects Versions: 1.3.9
> Reporter: Henri Yandell
> Assignee: Henri Yandell
> Priority: Minor
> Fix For: 1.3.10, 1.4.0
>
>
> The EL-Example has lots of 'disabled="${!empty pageScope}". This seems hugely confusing - why say that and not just 'true' or 'false'.
> At the minimum, need to explain when it's happening so people know a field is meant to be disabled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (STR-3055) Figure out the 'disabled="${!empty
pageScope}" in EL-Example
Posted by "Paul Benedict (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/STR-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41302 ]
Paul Benedict commented on STR-3055:
------------------------------------
You can't control it. It's just a fancy-pants way of getting true or false through an expression.
> Figure out the 'disabled="${!empty pageScope}" in EL-Example
> ------------------------------------------------------------
>
> Key: STR-3055
> URL: https://issues.apache.org/struts/browse/STR-3055
> Project: Struts 1
> Issue Type: Task
> Components: Apps
> Affects Versions: 1.3.9
> Reporter: Henri Yandell
> Assignee: Henri Yandell
> Priority: Minor
> Fix For: 1.3.10, 1.4.0
>
>
> The EL-Example has lots of 'disabled="${!empty pageScope}". This seems hugely confusing - why say that and not just 'true' or 'false'.
> At the minimum, need to explain when it's happening so people know a field is meant to be disabled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (STR-3055) Figure out the 'disabled="${!empty
pageScope}" in EL-Example
Posted by "Paul Benedict (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/STR-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Benedict updated STR-3055:
-------------------------------
Priority: Trivial (was: Minor)
> Figure out the 'disabled="${!empty pageScope}" in EL-Example
> ------------------------------------------------------------
>
> Key: STR-3055
> URL: https://issues.apache.org/struts/browse/STR-3055
> Project: Struts 1
> Issue Type: Task
> Components: Apps
> Affects Versions: 1.3.9
> Reporter: Henri Yandell
> Assignee: Henri Yandell
> Priority: Trivial
> Fix For: 1.3.10, 1.4.0
>
>
> The EL-Example has lots of 'disabled="${!empty pageScope}". This seems hugely confusing - why say that and not just 'true' or 'false'.
> At the minimum, need to explain when it's happening so people know a field is meant to be disabled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (STR-3055) Figure out the 'disabled="${!empty
pageScope}" in EL-Example
Posted by "Paul Benedict (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/STR-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Benedict updated STR-3055:
-------------------------------
Fix Version/s: (was: 1.4.0)
> Figure out the 'disabled="${!empty pageScope}" in EL-Example
> ------------------------------------------------------------
>
> Key: STR-3055
> URL: https://issues.apache.org/struts/browse/STR-3055
> Project: Struts 1
> Issue Type: Task
> Components: Apps
> Affects Versions: 1.3.9
> Reporter: Henri Yandell
> Assignee: Henri Yandell
> Priority: Trivial
> Fix For: 1.3.10
>
>
> The EL-Example has lots of 'disabled="${!empty pageScope}". This seems hugely confusing - why say that and not just 'true' or 'false'.
> At the minimum, need to explain when it's happening so people know a field is meant to be disabled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (STR-3055) Figure out the 'disabled="${!empty
pageScope}" in EL-Example
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/STR-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41299 ]
Henri Yandell commented on STR-3055:
------------------------------------
So, dumb question. How do you control the pageScope emptiness through the app?
I don't recall ever seeing the boolean result change; so things were always disabled.
> Figure out the 'disabled="${!empty pageScope}" in EL-Example
> ------------------------------------------------------------
>
> Key: STR-3055
> URL: https://issues.apache.org/struts/browse/STR-3055
> Project: Struts 1
> Issue Type: Task
> Components: Apps
> Affects Versions: 1.3.9
> Reporter: Henri Yandell
> Assignee: Henri Yandell
> Priority: Minor
> Fix For: 1.3.10, 1.4.0
>
>
> The EL-Example has lots of 'disabled="${!empty pageScope}". This seems hugely confusing - why say that and not just 'true' or 'false'.
> At the minimum, need to explain when it's happening so people know a field is meant to be disabled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (STR-3055) Figure out the
'disabled="${!empty pageScope}" in EL-Example
Posted by "Paul Benedict (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/STR-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41302 ]
Paul Benedict edited comment on STR-3055 at 6/28/07 5:54 AM:
-------------------------------------------------------------
You can't control it. It's just a fancy-pants way of saying true or false through an expression.
was:
You can't control it. It's just a fancy-pants way of getting true or false through an expression.
> Figure out the 'disabled="${!empty pageScope}" in EL-Example
> ------------------------------------------------------------
>
> Key: STR-3055
> URL: https://issues.apache.org/struts/browse/STR-3055
> Project: Struts 1
> Issue Type: Task
> Components: Apps
> Affects Versions: 1.3.9
> Reporter: Henri Yandell
> Assignee: Henri Yandell
> Priority: Minor
> Fix For: 1.3.10, 1.4.0
>
>
> The EL-Example has lots of 'disabled="${!empty pageScope}". This seems hugely confusing - why say that and not just 'true' or 'false'.
> At the minimum, need to explain when it's happening so people know a field is meant to be disabled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.