2011/10/4 Nestor Urquiza <nestor.urqu...@gmail.com>:
> Hi Mark,
>
> So you are suggesting Spring pet clinic application is broken?
There are many implementations of Pet Clinic out there. Yes, that one is broken.
> What
> would be the correct syntax then for the expresion that is failing?
You are not reading your answers, nor you are searching the archives.
This feature was discussed at least 3 times this summer.
${owner['new']} is direct equivalent of ${owner.new}
> Why tge latest version of jasper-el does not exhibit the problem when
> deployed in tomcat 7?
Is there "latest" version of it that is not already in tomcat 7? :]
>
>
>
> On Oct 3, 2011, at 5:40 PM, Mark Thomas <ma...@apache.org> wrote:
>
>> On 03/10/2011 13:58, Nestor Urquiza wrote:
>>> Hello,
>>>
>>> I was having this issue
>>> http://stackoverflow.com/questions/3879794/spring-3-petclinic-owner-new-invalid-expression-in-tomcat-7/7640435#7640435
>>>
>>> So I decided to try a couple of quick fixes and I solved it replacing the
>>> jasper-el.jar. I have blogged about the issue in
>>> http://thinkinginsoftware.blogspot.com/2011/10/tomcat-7-jstl-failed-to-parse.html
>>>
>>> Not sure if this is the list to post this issue. Hopefully it will help
>>> others.
>>
>> This is an application bug, not a Tomcat bug. Tomcat 7 just enforces the
>> requirements of the EL spec more strictly than Tomcat 6 did.
>>
>> You can disable this additional check using:
>> -Dorg.apache.el.parser.SKIP_IDENTIFIER_CHECK=false
>>
>> although the right solution is to fix the broken application.
>>
>> Mark
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
