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.
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 onwards. 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...
Marking this as RFE. This behaviour is not nice, I need to investigate this more.
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.