Menu
▾
▴
[ jEdit-devel ] [ jedit-Bugs-2920396 ] saxon7 + markersets = Exception when quitting jEdit 4.3
|
From: SourceForge.net <no...@so...> - 2010-01-02 05:46:42
|
Bugs item #2920396, was opened at 2009-12-24 01:48 Message generated for change (Comment added) made by shlomy You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100588&aid=2920396&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: Robert Schwenn (rschwenn) Assigned to: Nobody/Anonymous (nobody) Summary: saxon7 + markersets = Exception when quitting jEdit 4.3 Initial Comment: With both the XQuery and MarkerSets Plugins loaded, I get a message box when I quit jEdit. The message box (about 10 m long :-) seems to show an exception and has to be confirmed. I havn't seen this message box before 4.3 release. Activity log is attached. jEdit 4.3 MarkerSets Plugin 0.3 XQuery Plugin 0.8.0 SUN JRE 1.6.0_17 Windows XP SP3 ---------------------------------------------------------------------- >Comment By: Shlomy Reinstein (shlomy) Date: 2010-01-02 07:46 Message: I just changed MarkerSets to use the platform default XML implementation instead of using whatever is configured by other plugins (like xquery). Can you check with the trunk version of MarkerSets to see if this problem is solved? The only thing I am not sure about is whether the implementation I use (com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl) is available with any JVM. ---------------------------------------------------------------------- Comment By: Robert Schwenn (rschwenn) Date: 2010-01-01 19:20 Message: @ Shlomy: I don't have to kill jEdit. After I have confirmed a message box jEdit quits normally. ---------------------------------------------------------------------- Comment By: Shlomy Reinstein (shlomy) Date: 2009-12-31 20:15 Message: The problem does not seem to be in parsing the XML - the problem is in writing it. MarkerSets uses DocumentBuilderFactory to simplify both reading and writing XML - and, as it turns out, plugins can install their own XML implementations (like saxon in this case) which cause MarkerSets unintentionally to use them. I am considering to change MarkerSets to read/write XML by itself without using the DocumentBuilderFactory. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2009-12-31 20:02 Message: If there is indeed a bug in how markersets gets the XML parser, that should be fixed in any case. Why is it none of the other plugins that need to parse XML run into this problem? Maybe xquery also needs to be updated to saxon9 (the current version of saxon)? ---------------------------------------------------------------------- Comment By: Shlomy Reinstein (shlomy) Date: 2009-12-31 18:41 Message: Does this cause jEdit to hang during exit, so you have to kill it? If not, I'd mark this as a MarkerSets problem, not a core problem. ---------------------------------------------------------------------- Comment By: Robert Schwenn (rschwenn) Date: 2009-12-26 14:44 Message: The MarkerSets Plugin works well when the XQuery plugin (more exactly saxon7.jar) isn't loaded. ---------------------------------------------------------------------- Comment By: Shlomy Reinstein (shlomy) Date: 2009-12-26 07:22 Message: I can change MarkerSets to write the XML file in a different way that would prevent other plugins from breaking it. I had no idea until recently that other plugins may be modifying the way the XML is created by installing their own XML builder. But, I'd like to verify that it's really a problem caused by the other plugins. Can you try the same thing (with the space in the path name) when none of the XML-related plugins is installed? ---------------------------------------------------------------------- Comment By: Robert Schwenn (rschwenn) Date: 2009-12-26 02:05 Message: The message "Illegal character in path at index 13" seems to be related to the space in the path name. I tried a settings directory without spaces in the path name and another exception occurs. Maybe we should wait for the fix of bug #2920802 (https://sourceforge.net/tracker/?func=detail&atid=565475&aid=2920802&group_id=588). The exceptions are thrown when toggling a marker in a set, too. However, this is a regression of the 4.3 release (pre18 works). ---------------------------------------------------------------------- Comment By: Shlomy Reinstein (shlomy) Date: 2009-12-26 00:30 Message: The exception shows the following line: javax.xml.transform.TransformerException: java.net.URISyntaxException: Illegal character in path at index 13: /C:/Dokumente und Einstellungen/sc/.jEdit_43/plugins/marker.MarkerSetsPlugin/markerSets.xml I have seen bug reports about exceptions from MarkerSets when some XML builder plugin is installed. MarkerSets uses the DocumentBuilderFactory to get a document builder, which creates the xml configuration file of the plugin. Apparently, this is never a problem with the default document builder of java, but some plugins install their own (e.g. saxon7.jar in this case?) and these fail to write. Can you try without XQuery and see what would be the contents of the faulty line (13) in the MarkerSets.xml file? Maybe I can work around this problem by emitting the configuration differently. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100588&aid=2920396&group_id=588 |