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.
Sierra Build 020812 when erroroneous web.xml is saved, an "Invalid XMl file" dialog opens up saying "There were errors found when validating XML document. See output window for errors. Save anyway ?" This makes "Red-X" bade to appear on web.xml * when user wants to know the errors later, if there is a menuitem, to validate this XML ,it would prove useful. * During my test, i had not changed anything in web.xml, red-x started appearing . I had to execute the web module to find out what exactly is the error.
Changing to Enhancement - sounds like a usability improvement request.
Implemented CheckXMLCookie and ValidateXMLCookie for DDDataObject. Thus, "Check XML" and "Validate XML" actions appear in the contextual menu. Since then both actions are enabled also in the editor window toolbar. Fixed in trunk.
** I don't see this when i right click on web.xml in FS Explorer. I could see these context menu's only when i right click on opened web.xml in source editor. You may want to reopen this issue and have it fully fixed.
Milan, You may please see my earlier comments. Just to bring this to your attention, i am repoening this case.
A user comment on this... XML files display the XML tools on their context menu (Check/Validate/etc). The web.xml file does not. Does NB consider it a 'webapp' file first and not as an XML file as well? I think it is important to fix this since it is inconsistent behavior for XML files and since the system does validate the file when saving, but then does not give you the option to revalidate if there were problems.
There is no simple way how add the "Check XML" and "Validate XML" actions to web.xml node. There is missing XML/tools API, which should provide some public CheckXMLAction and ValidateXMLAction classes. I added dependancy on 20532.
Apologies, I should have tracked this bug better. There is an additional problem here because the Servlet 2.3 spec doesn't require the deployment descriptor to be valid per the DTD. So we probably shouldn't show it as invalid unless we're sure it is (i.e. the server won't start).
Fixed for 3.6