[ jEdit-devel ] [ jedit-Plugin Bugs-2810050 ] XMLPlugin XercesParserImpl null CompletionInfo

[SourceForge.net <no...@so...>]

Plugin Bugs item #2810050, was opened at 2009-06-21 21:19
Message generated for change (Tracker Item Submitted) made by gknittl
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=565475&aid=2810050&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Greg Knittl (gknittl)
Assigned to: Nobody/Anonymous (nobody)
Summary: XMLPlugin XercesParserImpl  null CompletionInfo

Initial Comment:
requirements:
-XML Plugin relax-ng branch
-the buffer is validated by an XML schema
-the buffer contains an error that prevents Xerces from parsing all the way to the end, such as a fundamental syntax error like an unclosed element or an incomplete entity
-the XML plugin has parsed the invalid buffer 
result:
the XML Plugin no longer displays schema related completions.

I recreate this on demand by adding a < as a new element or & and manually invoking the XML parser. 
I get into this state fairly often in natural use by switching buffers in mid element. Enabling parsing on saving or by keystroke
will result in parsing invalid buffers quite easily too.

The XML plugin builds CompletionInfo each time it parses the buffer.
For buffers validated by XML Schemas,  XercesParserImpl.endElement() builds the completion info through Xerces.
The plugin builds CompletionInfo when endElement() receives the last end tag that Xerces parses. In the case of a structural error, Xerces 
stops parsing. endElement() doesn't get the last tag and the plugin builds no completion information.

The schema could change while the buffer is loaded, so it makes sense to reload it on each parse, 
or at least to check if it has changed and update it if necessary. As time permits, will investigate if there
 is a more robust way of capturing the schema, perhaps at startDocument. 


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=565475&aid=2810050&group_id=588