I was digging into this, and the problem doesn't seem to be on the iterator
tag itself, when this line is executed (on IteratorComponent):
iterator = MakeIterator.convert(findValue(value));
findValue is returning an Array with an extra element at the end, null,
which is causing the extra
--- Musachy Barroso [EMAIL PROTECTED] wrote:
findValue is returning an Array with an extra
element at the end, null, which is causing the extra
iteration, I think. I'm not really sure why OGNL
is doing that. To be continued ...
It's not returning an extra element, the element is
there--it's
Yeah, I was writing about that now, dumb me, I spent half an hour when I
noticed that :)
if ((id != null) (currentValue != null)) {
//pageContext.setAttribute(id, currentValue);
//pageContext.setAttribute(id, currentValue, PageContext.REQUEST_SCOPE);
stack.getContext().put(id, currentValue);
--- Musachy Barroso [EMAIL PROTECTED] wrote:
Yeah, I was writing about that now, dumb me, I spent
half an hour when I noticed that :)
The only reason I can say I hate it when that
happens is 'cuz I always do stuff like that and I
hate it when that happens.
I'm testing to see if nothing else
I logged :
https://issues.apache.org/struts/browse/WW-2024
just to help my memory :)
musachy
On 7/2/07, Dave Newton [EMAIL PROTECTED] wrote:
--- Musachy Barroso [EMAIL PROTECTED] wrote:
Yeah, I was writing about that now, dumb me, I spent
half an hour when I noticed that :)
The only
tom tom wrote:
because I got if statements and logic inside, it is
not merely diplaying the value.
You can always refer to the current iteration value as top
-Dale
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
I did further investigation,
I think this is a bug, I think this is a very scary
bug.
You dont need three iterators, I could reproduce this
very easily,
In your action class have the following,
String[] testArray = new String[5];
testArray[0]=test0;
Yes this definitely is a bug to me,
How can I make a JIRA issue for this, what is the URL,
I Dont think we can go to production with this issue,
Is there a way to get a patch for this,
Should we have to wait for the next release ?
Thanks,
--- Dave Newton [EMAIL PROTECTED] wrote:
--- tom
Hi,
What did you mean by
is an issue iff you're
using an id
What else can I use to get the value inside an
Iterator?
Thanks
--- Dave Newton [EMAIL PROTECTED] wrote:
--- tom tom [EMAIL PROTECTED] wrote:
WHAT it prints is following Issue is for the 4th
index also it prints test, it
--- tom tom [EMAIL PROTECTED] wrote:
What did you mean by
is an issue iff you're using an id
What else can I use to get the value inside an
Iterator?
Stack notation, like [0].foo etc. It's a kludgy
workaround for this situation but it should work.
d.
index is variable, without introducting a scriptlet
with int i=0 and the have i++, Is there any other
inbuild way?
Thanks
--- Dave Newton [EMAIL PROTECTED] wrote:
--- tom tom [EMAIL PROTECTED] wrote:
What did you mean by
is an issue iff you're using an id
What else can I use to
What?
[n] accessing the stack at the given level: [0] is the
root, [1] is the previously-pushed item, etc.
s:iterator...
s:iterator...
s:property value=[0]/ %-- inner it. value
--%
s:property vlaue=[1]/ %-- outer it. value
--%
/...
(AFAIK, anyway; can't test at the moment.)
d.
---
Have you tried this?
s:iterator value=#session.testArray
Value of the arry is
s:property /
br
/s:iterator
tom tom wrote:
I did further investigation,
I think this is a bug, I think this is a very scary
bug.
You dont need three iterators, I could reproduce this
very easily,
In your
Thanks,
As I mentioned earlier, I need to have id,
because I got if statements and logic inside, it is
not merely diplaying the value.
This bug needs to be fixed.
Till then be carefull
--- Adam Ruggles [EMAIL PROTECTED] wrote:
Have you tried this?
s:iterator value=#session.testArray
Take a look at the value stack via the debug tag.
Usually the property tag will keep stepping through the value stack
until a getter for the property is found (the object for the current
iteration is placed on the top of the value stack). Although, if you
are explicitly defining the object
Hi,
I got three iterations which I tried as below in the
jsp, First two and Array of certain DTO and last
iterator is a String array. There is no jsp
compilation error, but the issue is it produced
misleading results.
Is there any limitation in S2 for the depth of the
iteration. Is this way of
16 matches
Mail list logo
