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.
Various JSF 2.0 problems encountered while using Netbeans 6.8 build 9-14-2009. The Description of the JSF File Type when using the New File wizard only mentions JSP pages and not Facelets. Needs updating for JSF 2.0 An index.xhtml and template.xhtml are create when a new JSF file is created using the New File wizard even if you don't want them. They are also created when adding the JSF Framework to a project. Both the Add Framework and New File wizards should have a checkbox to create a template. It could be skipped by default and have a New JSF Template wizard as a separate thing. Don't force unwanted files on the user, it'd be like automatically making a session façade every time a JPA entity class was created. Using either the url pattern in the web.xml or the namespace declaration, the HTML validation rules should be disabled by default for any .xhtml page that is actually a facelet. Custom validation rules would work to but I assume The JSF Palette needs to contain all the Facelet tags. It'd also be nice to include the tag libraries themselves in the palette so you can drag them onto a page any they'd get added to the html tag.
Meant to say "Custom validation rules would work to but I assume that those would take more time to implement"
An additional validation problem with Facelets. Even if you disable HTML validation for a Facelet page the Tasks window will still show all the HTML validation problems.
When using the New File wizard it is confusing that there is a "JSF" choice underneath the "Web" category and a "JSF Page" choice underneath the "JavaServer Faces" category that do the same thing. The "Web -> JSF" option should be removed.
Another error. When editing a JSF 2.0 Facelet some of the EL expressions are incorrectly flagged as errors. For example: <h:dataTable value="#{stocks.allStocks}" var="stock"> <h:column> <f:facet name="header">Symbol</f:facet> #{requestScope.stock.symbol} </h:column> <h:column> <f:facet name="header">Price</f:facet> #{stock.price} </h:column> </h:dataTable> The #{requestScope.stock.symbol} and #{stock.price} expressions are both underlined in red. The error message in NetBeans is 'The bean "..." is not found.'. Additionally when trying to autocomplete EL expressions the "requestScope" is missing from the list.
Even creating a new JSF Managed Bean causes the unwanted JSF template files to be created, it is highly annoying. Does every single JSF artifact cause these template files to be created? Another bug: If you manually add the JSF 2.0 Servlet to the web.xml NetBeans will detect it an show that JSF is an added Framework in the project properties. However for some reason the "Preferred Page Language" under the JavaServer Faces framework configuration defaults to JSP. Now all the unwanted JSF templates are JSP pages by default.
Several tags from the Facelet HTML tag library are missing descriptions when attempting to use auto-completion. The tags are: body, button, head, link, outputScript, and outputStyleSheet.
Probably related to the missing descriptions when attempting to use auto-completion. The following tags will not have any of their attributes auto-completed: body, button, head, link, outputScript, and outputStyleSheet.
I split problems into individual issues which can be addressed by different developers: * code completion problems - issue 172824 * xhtml validation problems - issue 172826 * jsf palette - issue 172827 * jsf wizard problems - 172828 Issues which are already fixed in recent dev builds: * manually adding JSF 2.0 Servlet results in JSP preferred language
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