This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 66730 - Some error messages are not self-explaining
Summary: Some error messages are not self-explaining
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: JSP Parser (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@javaee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-13 16:06 UTC by Jiri Prox
Modified: 2016-07-07 08:54 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Prox 2005-10-13 16:06:01 UTC 
NB 5.0 build 20051012220

Some of the error messages can be missleadnig when wrong combination of
atributes of standard jsp actions are provided.

Here is the list:
1) jsp:useBean action:
When 'class' nor 'type' attribute are not provided error message
'jsp.error.useBean.missingType' is shown.

When 'beanName' is provided and 'type' attribute is omitted error message
'jsp.error.useBean.missingType' is shown

When 'class' and 'beanName' are provided together error message
'jsp.error.useBean.notBoth'  is shown

2) jsp:setProperty action
When 'param' and 'value' attributes are provided error message
'jsp.error.setProperty.invalid' is shown

3) jsp:element action
When 'name' attribute is omitted missleading message is shown:
...'NegativeArraySizeException'
Comment 1 Marek Fukala 2005-10-14 13:56:48 UTC 
These messages are gotten directly from our patched tomcat's parser. We would
have to implement a map of "tomcat messages" to "human friently" messages which
is doable. AFAIK the messages should be the same as messages provided by tomcat
compiler when you want to execute the broken page. No time for this now.
Comment 2 Marek Fukala 2005-10-20 17:24:46 UTC 
It is rather an enhancement
Comment 3 Martin Balin 2016-07-07 08:54:17 UTC 
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue.

Thanks for your cooperation,
NetBeans IDE 8.2 Release Boss