[markt]

The following JSP generates an invalid character warning, although the JSP is perfectly valid.

=== JSP Start ===
<%@ page isELIgnored=”true” %>${<%= “Hello, world!” %>}
=== JSP End ===

The issue is the isELIgnored=”true”. If this were isELIgnored=”false” then the JSP would be invalid. The validator should take the setting of isELIgnored into account.

What makes fixing this more ‘entertaining’ is that isELIgnored can be set in anywhere in the translation unit. This means it could be set after you have already parsed content that contained EL syntax.

After trying various hacks to handle this in Tomcat we eventually took a two phased approach to parsing. The first phase parses and validates the page directives and the second phase handles the rest. I suspect a complete solution to this issue will require a similar approach in the JSP validator.

On my Mac this generates an error rather than a warning. I haven’t taken the time to figure out why.

System setup is (windows):
*** Date:
Monday, 16 February 2009 22:47:14 o’clock GMT

** System properties:
OS=WindowsXP
OS version=5.2.0
Java version=1.5.0_17

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 7.0
Build id: 7.0-20081201

*** Eclipse details:
Eclipse SDK

Version: 3.4.1
Build id: M20080911-1700

Eclipse Platform

Version: 3.4.1.r341_v20080731-9I96EiDElYevwz-p1bP5z-NlAaP7vtX6Utotqsu
Build id: M20080911-1700

Eclipse Java Development Tools

Version: 3.4.1.r341_v20080709-0800-7o7tEAfEF_U5qyUgrb2HAp539P97
Build id: M20080709-0800

Eclipse Plug-in Development Environment

Version: 3.4.1.r341_v20080731-7T7U0E9mlRIuGUYviF_VP
Build id: M20080703-0800

Eclipse Project SDK

Version: 3.4.1.R34x_v20080827-7O7S78C2J40sK2o_ALcK8tLN_yZSJeg0P-3EtL4Ra90kv
Build id: M20080911-1700

Eclipse Graphical Editing Framework GEF

Version: 3.4.1.v20080806-67718083A56B4H2A3213573
Build id: 200809101400

Eclipse RCP

Version: 3.4.100.r341_v20080814-989JESIEdAciFYfkZZsBfSwQ2341
Build id: M20080703-0800

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
C:\Program Files (x86)\eclipse\\plugins\org.eclipse.platform_3.3.101.v200809111700\splash.bmp
-launcher
C:\Program Files (x86)\eclipse\eclipse.exe
-name
Eclipse
–launcher.library
C:\Program Files (x86)\eclipse\\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731\eclipse_1115.dll
-startup
C:\Program Files (x86)\eclipse\\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
-vm
C:\Program Files (x86)\Java\jre1.5.0_17\bin\client\jvm.dll

[Loyal Water]

I have asked the dev team to look into this issue. Thank you for bringing it to our attention.

[Author]

Posts