[JIRA] Created: (NAWSAKABRAZIL-12) Confusing local scoping in naws really doesn't make any sense
- From: "digitalrinaldo (JIRA)" <jira-no-reply@kenai.com>
- To: issues@nawsakabrazil.kenai.com
- Subject: [JIRA] Created: (NAWSAKABRAZIL-12) Confusing local scoping in naws really doesn't make any sense
- Date: Wed, 6 Oct 2010 13:39:25 +0000 (GMT+00:00)
- Auto-submitted: auto-generated
Confusing local scoping in naws really doesn't make any sense
-------------------------------------------------------------
Key: NAWSAKABRAZIL-12
URL: http://kenai.com/jira/browse/NAWSAKABRAZIL-12
Project: nawsakabrazil
Issue Type: Bug
Environment: All
Reporter: digitalrinaldo
Why do I have to add namespace=local. Having the namespace change on
different is very confusing and difficult to remember.
the namesapce="local" is needed or flatKey since one is in request and the
other is local.
<foreach name=r property="${queryResult}.rows">
<set name=flatKey value="" namespace="local"/>
<foreach name=a list="${attributes}">
<set name=k value="${prefix}.\${a}.\${r}" />
<set name=v value="\${\${k}}" />
<get name=v><br>
<append name=flatKey value="\${\${k}}" delim="."/>
<get name=flatKey><br>
</foreach>
</foreach>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://kenai.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
[JIRA] Created: (NAWSAKABRAZIL-12) Confusing local scoping in naws really doesn't make any sense |
digitalrinaldo (JIRA) | 10/06/2010 |





