Bug 1182618

Summary: Tomcat7 - NoSuchElementException for attribute with empty string in custom tag
Product: [JBoss] JBoss Enterprise Web Server 2 Reporter: Libor Fuka <lfuka>
Component: tomcat7Assignee: Coty Sutherland <csutherl>
Status: CLOSED ERRATA QA Contact: Libor Fuka <lfuka>
Severity: high Docs Contact:
Priority: unspecified    
Version: 2.1.0CC: csutherl, jclere, jdoyle, mbabacek, mhasko, mturk, weli
Target Milestone: ---   
Target Release: One-off release   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-16 15:21:55 UTC Type: Support Patch
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1161215, 1182834    
Bug Blocks:    
Attachments:
Description Flags
jasper.jar none

Description Libor Fuka 2015-01-15 15:01:13 UTC 
Description of problem:
From Upstream:

A tld has an attribute which could be an empty string. Example is below. Here 'indicator' attribute is provided as "".
<dmf:requiredfieldvalidator 
	name='<%=Login.CONTROL_USERNAME_VALIDATOR%>' 
	controltovalidate='<%=Login.CONTROL_USERNAME%>' 
	nlsid='<%=Login.MSG_USERNAME_REQUIRED%>' 
	indicator=""
/>
However, while compiling this in jsp resulted in the following exception:

message Unable to compile class for JSP
description The server encountered an internal error that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: Unable to compile class for JSP

Version-Release number of selected component (if applicable):
EWS 2.1.0 Tomcat7
Comment 2 Libor Fuka 2015-01-20 07:24:09 UTC 
We need also jar attachment for EWS zip distribution.
Comment 3 Weinan Li 2015-01-20 08:17:16 UTC 
Created attachment 981769 [details]
jasper.jar
Comment 4 Libor Fuka 2015-01-23 08:04:04 UTC 
Verified with attachment jasper.jar
Comment 6 errata-xmlrpc 2015-02-16 15:21:55 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0232.html