[jboss-jira] [JBoss JIRA] (WFLY-3267) Confusing error message when tag file's attribute type is unknown

[Paul Benedict (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964197#comment-12964197 ] 

Paul Benedict commented on WFLY-3267:
-------------------------------------

Yes, I verify the error message is the same in 8.1.0.CR1. I can tell by the stacktrace the message is generated by the Jasper compiler -- which is not a JBoss component. If you want to open up a corresponding ticket in Tomcat (owners of jasper?), that would be ideal.
                
> Confusing error message when tag file's attribute type is unknown
> -----------------------------------------------------------------
>
>                 Key: WFLY-3267
>                 URL: https://issues.jboss.org/browse/WFLY-3267
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Undertow)
>    Affects Versions: 8.0.0.Final
>            Reporter: Paul Benedict
>            Assignee: Remy Maucherat
>            Priority: Trivial
>
> I have a JSP tag file that requires a "size" attribute: 
> {code}
> <%@ attribute name="size" required="true" type="Long" %>
> {code}
> Because the type accidentally wasn't a FQN (it should have been a {{java.lang.Long}}), this error was generated:
> {code}
> JBWEB004193: Unknown attribute type (size) for attribute Number
> {code}
> The message doesn't make any sense. "size" isn't the attribute type and the attribute is not "Number". A possible fix:
> {code}
> JBWEB004193: Unknown type (Number) was declared for attribute (size)
> {code}
> PS: It's really important to talk about the "declaration" here because the tag file isn't mentioned at all in the exception. The Jasper compiler only reports the enclosing JSP, which makes it look like the problem is with the usage not the tag file itself.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira