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 97506 - Visual Editor: Errors passed from child to parent
Summary: Visual Editor: Errors passed from child to parent
Status: NEW
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 5.x
Hardware: PC All
: P3 blocker with 1 vote (vote)
Assignee: _ sandipchitale
Depends on:
Reported: 2007-03-08 21:06 UTC by yossarian
Modified: 2007-03-22 23:49 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description yossarian 2007-03-08 21:06:37 UTC
RFE - Visual designer handling of EL errors

When a component has an el error is renders with a red x in the corner and and 
error message. The visual designer stops rendering components from this point 

However when a container (gridpanel, property sheet et al) has a child 
component with an EL error the error is passed right up the tree to the top 
level object short of the form.  This sucks.  It's a mission to figure out 
which component is in error and one quite often finds oneself doing a text 
search of the jsp or similar techniques.

RFE #1:  Stop the errors passing to the parent (ie extend the existing 
mechanism that stops errors passing to the form, body and html elements)

RFE #2:  Improve the visual look of a component in error state.  More color, 
better messages.

RFE #3:  Allow rendering to continue with the next component after the 
component in error.

Test Case:

Drop two static text components on a form.  Bind the second one to a non-
existent field in a dataprovider.  The second will show an error -- this is how 
the page should look.

Now do the same with the first static text component.  The second component 
disappears.  Which one is which now?

Now drag the static text components to a gridpanel.  Everything is just one big 
error now.  Good luck if you have dozens of components in that gridpanel and 
you don't know which one is causing the problem...
Comment 1 Peter Zavadsky 2007-03-22 21:43:20 UTC
Marking this as RFE.
This behaviour is not nice, I need to investigate this more.
Comment 2 Peter Zavadsky 2007-03-22 23:49:18 UTC
The first problem is the jsf rendering, it seems once encountered the problem,
it interrupts to render further componnets.
Passing to insync first. Designer doesn't have anything more to paint, just what
is provided.