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); } I'm testing to see if nothing else breaks by removing the currentValue != null condition musachy On 7/2/07, Dave Newton <[EMAIL PROTECTED]> wrote:
--- 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 just a null. The issue is because the stack element at the "id" key is only being set if the value isn't null, meaning (I guess) that the previous value will remain (which also explains what the OP is seeing). d. ____________________________________________________________________________________ Yahoo! oneSearch: Finally, mobile search that gives answers, not web links. http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- "Hey you! Would you help me to carry the stone?" Pink Floyd