brooksie commented on pull request #2613: URL: https://github.com/apache/netbeans/pull/2613#issuecomment-821233526
Geertjan, what specifically do you need to see in order to make you happy? The proposed fix is as simple as it gets - a 1 line fixed-text addition to a template file. It would be easy enough to amend the reproducer to demonstrate that the error goes away when the namespace is added - that's exactly what I do manually (and repeatedly) at the moment to resolve the issue myself as a netbeans user. Including it in the default generated template takes away those manual, repeated edits. But your question is wider than that - are there any situations where including this in the generated ui:composition header would break the code. Perhaps you need to pose your question to your Netbeans JSF expert, or to someone in the expert panel working on the JSF specifications? Bauke Scholtz comes to mind. FYI here is a couple of postings on Stackoverflow from Bauke Scholtz, known there as BalusC, showing the correct usage of ui:composition as a facelets template client. They all include the basic xmlns: https://stackoverflow.com/questions/4792862/how-to-include-another-xhtml-in-xhtml-using-jsf-2-0-facelets https://stackoverflow.com/questions/8500894/how-to-change-head-elements-of-a-page-when-using-uicomposition From wikipedia: https://en.wikipedia.org/wiki/Facelets#Templating (see "template client" heading) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
