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 110281

Summary: XML editor does not show errors in malformed XML document
Product: xml Reporter: jfurmankiewicz <jfurmankiewicz>
Component: CodeAssignee: issues@xml <issues>
Status: NEW ---    
Severity: blocker    
Priority: P1    
Version: 6.x   
Hardware: All   
OS: Windows XP   
Issue Type: ENHANCEMENT Exception Reporter:

Description jfurmankiewicz 2007-07-19 13:18:12 UTC 
Consider this XML snippet:
<?xml version="1.0" encoding="UTF-8"?>
<library xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
        xmlns='http://www.laszlosystems.com/2003/05/lzx'
        xsi:schemaLocation='http://www.laszlosystems.com/2003/05/lzx http://www.openlaszlo.org/lps/tools/lzx.xsd'>
    
            <security>test</allow>
</canvas>

It is malformed (<security> tag not closed, </allow> closing tag does not have the equivalent opening tag).

But, the XML editor does not indicate any sort of error. The tag or line is not highlighted, the document node in the
Projects view does not have an error icon on it, nothing.

Everything looks as if this was a correctly formed XML document, even though it isn't.

If you open this file in IE, you get the obvious error:



End tag 'allow' does not match the start tag 'security'. 

            <security>test</allow>
----------------------------^


happens in NB 6.0M10
Comment 1 Samaresh Panda 2007-07-19 16:39:04 UTC 
True, however we may not be able to fix it for 6.0. This is more like a feature and fix needs a thorough planning and
careful thought. No just xml, but we also have to look at xsds and many more files.

I appreciate you filing these issues. We need more such requirement in XML land. I'm not completely ruling out a fix for
this in 6.0...will revisit if time permits.
Comment 2 jfurmankiewicz 2007-07-19 16:50:31 UTC 
I understand. Please bring it up during your next dev meeting, I think it's a big hole in the current functionality. But
I can also understand it's probably a significant effort if it's missing right now.