Re: T4.1.3 loop index issues, migrating from 4.0.2

Thanks for your help Jessie. Fix you applied to the 4.1.4-SNAPSHOT has fixed our issue. We have run into another issue in the migration which I'll post about separately... Dom Couldwell Global Markets Research +1(212)250-7082 --- This e-mail may contain confidential and/or privileged

Re: T4.1.3 loop index issues, migrating from 4.0.2

HmmI'll look at it later tonight and put out a fix - if I'm able to re-produce it outside of Tapestry somehow. On Oct 31, 2007 5:11 PM, Dom Couldwell [EMAIL PROTECTED] wrote: Any ideas as to when we might get a fix for this? We're stuck in terms of migrating to 4.1.3 until we get a fix.

Re: T4.1.3 loop index issues, migrating from 4.0.2

Any ideas as to when we might get a fix for this? We're stuck in terms of migrating to 4.1.3 until we get a fix. Thanks, Dom --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the

Re: T4.1.3 loop index issues, migrating from 4.0.2

Tried Andy's work around but no joy (stack track below). Have raised another JIRA (http://jira.opensymphony.com/browse/OGNL-131) yell if you need more details. Dom 2007-10-25 09:09:57,763, ERROR, [com.db.rdq.web.tapestry.html.RDQException], line 22, org.apache.tapestry.BindingException

Re: T4.1.3 loop index issues, migrating from 4.0.2

I had a typo in my suggestion - happens with such long expressions I guess ;) I meant selected=ognl:getTab().getSearchCriteriaSelections().get(currentFilterGroupIndex)[currentFilterIndex] Dom Couldwell wrote: Tried Andy's work around but no joy (stack track below). Have raised another

T4.1.3 loop index issues, migrating from 4.0.2

Thanks to Jessie for his help fixing our last issue (We've updated to the ognl 2.7.2 snapshot which fixed it) but and have run into another issue migrating form 4.0.2 to 4.1.3. The following works fine under 4.0.2: select jwcid=@Select multiple=literal:false

Re: T4.1.3 loop index issues, migrating from 4.0.2

looks like an issue during rewind - take a look at all those parameters and the hints for the @For component at http://tapestry.apache.org/tapestry4.1/components/general/for.html If the form worked in 4.0 and you weren't getting any |StaleLinkExceptions|, then using volatile=true should

Re: T4.1.3 loop index issues, migrating from 4.0.2

Updated first For loop to: select jwcid=@Select multiple=literal:false size=10 onchange=ognl:'searchSubmit(\''[EMAIL PROTECTED]@INSTRUMENT_GROUP+'\',0);' div jwcid=@For source=ognl:tab.searchItems

Re: T4.1.3 loop index issues, migrating from 4.0.2

well, it must be ognl related after all... In http://jira.opensymphony.com/browse/OGNL-130 you mentioned you tried selected=ognl:getTab().getSearchCriteriaSelections().get(currentFilterGroupIndex).get(currentFilterIndex) Well, I'm wondering if

Re: T4.1.3 loop index issues, migrating from 4.0.2

Another ognl jira ticket with as much specific information as possible would help me either way. Since you are getting errors that mention OgnlRuntime I'm thinking this isn't a compile time issue at all so would probably consider it more important than most to fix. (assuming I'm able to