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 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
--- 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
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:
> 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--
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 iterati
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?
>
>
> Value of the arry is
>
>
Have you tried this?
Value of the arry is
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 action class have the following,
String[] testArray = new Stri
What?
[n] accessing the stack at the given level: [0] is the
root, [1] is the previously-pushed item, etc.
<%-- inner it. value
--%>
<%-- outer it. value
--%>
(AFAIK, anyway; can't test at the moment.)
d.
--- tom tom <[EMAIL PROTECTED]> wrote:
> index is variable, without intro
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
--- 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.
_
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
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:
> --- t
--- tom tom <[EMAIL PROTECTED]> wrote:
> WHAT it prints is following Issue is for the 4th
> index also it prints test, it should print empty
>
> Value of the arry is test0
> Value of the arry is test1
> Value of the arry is test2
> Value of the arry is test
> Value of the arry is test
I agree; t
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";
tes
15 matches
Mail list logo
