counter-intuitive white space handling of function-signature when defining custom functions.

[glassfishrobot]

I am using org.apache.jasper.jspC from glassfish.jar version: 2.2.2_v201108011116

When defining custom functions in *.tld. The white space handling by JspC compiler is not intuitive. See the example below.

java.lang.String
getName()

There must be a white space character immediately after return type ('java.lang.String' in this case), even if the rest of the signature definition is on a separate line. a new line character or a tab following the return type will cause an error.

What's more when this happens, the JspC simply output an error of invalid signature without mentioning which line or which function's signature is invalid. This make debugging very difficult as white spaces, tabs, new line characters are not often invisible.

Environment

Linux, Ubuntu-10, Jetty application server.

[glassfishrobot]

@glassfishrobot Commented
Reported by yantan

[glassfishrobot]

@glassfishrobot Commented
This issue was imported from java.net JIRA JSP-24

[glassfishrobot]

• Issue Imported From: https://github.com/javaee/javaee-jsp-api/issues/24
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @glassfishrobot

[markt-asf]

This bug was present in the upstream Apache Tomcat JSP engine (Jasper) but had not been reported upstream. The bug has now been fixed in Tomcat.