I am an open source developer myself and I *love* when the users submit patches that work or at least create intelligent Jira's :-)
But that's not the point here. Even though there is an OGNL-11 bug report, this is not a bug. This is a new "feature" of Tapestry 4.1. No matter was else was said in this thread, there is clearly a consensus between Tapestry commiters and users about what is causing it. The disagreement is what (if anything) should be done about that. So it will not help if I open another bug report saying "my @For loop is broken" - it will not get fixed unless we all agree that 4.0 scriptable behavior was a good thing :-) Cheers, Andrus Kalle Korhonen-2 wrote: > > Exclude the version that comes with 4.1.2 and fall back to 2.6.7. But, I > think it's the responsibility of us, the users, to iron out the bugs in > the > expressionCompiler. I mean it's the least we can do. The benefits far > outweigh the current issues from my perspective and Jesse's more than > willing to fix any emerging issues. Everybody wants it, but if no one but > him is willing to put down some effort, it'll never be finished. > > Kalle > -- View this message in context: http://www.nabble.com/Class-cast-exception-in-ASTChain%2C-Bug-OGNL-11-tf4054151.html#a12183517 Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
