Please confirm soln: [Bug 22226] Tomcat throws JasperExceptioninstead of NumberFormatException when parameter can't convert to bean property

2003-08-14 Thread Tim Funk
The spec says for jsp:setProperty:
A conversion failure leads to an error, whether at translation time or 
requesttime.

From a compliance point of view, it looks like tomcat is OK that is throws a 
JasperException.

But from a user (web developer) point of view, I would think this sucks. But 
am I correct that this is not a bug? (So I can resolve as invalid)

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6

-Tim



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Please confirm soln: [Bug 22226] Tomcat throws JasperExceptioninstead of NumberFormatException when parameter can't convert to bean property

2003-08-09 Thread Kin-Man Chung
You are right in that this is not a spec conformant issue and is
therefore not a bug.

Except for some exceptions, most exceptions are caught and rethrown
as JasperExceptions.  Making exceptions would just, well, complicate
things.  :-)

-Kin-man

 Date: Fri, 08 Aug 2003 09:00:30 -0400
 From: Tim Funk [EMAIL PROTECTED]
 Subject: Please confirm soln: [Bug 6]   Tomcat throws JasperException 
instead of NumberFormatException when parameter can't convert to bean property
 To: Tomcat Developers List [EMAIL PROTECTED]
 
 The spec says for jsp:setProperty:
 A conversion failure leads to an error, whether at translation time or 
 requesttime.
 
  From a compliance point of view, it looks like tomcat is OK that is throws a 
 JasperException.
 
 But from a user (web developer) point of view, I would think this sucks. But 
 am I correct that this is not a bug? (So I can resolve as invalid)
 
 http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6
 
 -Tim
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]