Conversation
Signed-off-by: Jean-Yves Tinevez <jean-yves.tinevez@pasteur.fr>
Contributor
|
Same exception when trying to open a BigDataViewer XML. Stephan On October 9, 2015 7:21:21 AM EDT, Jean-Yves Tinevez notifications@github.com wrote:
|
ctrueden
added a commit
that referenced
this pull request
Oct 9, 2015
Update jdom2 to v2.0.6 Currently, some of the tools that rely on JDom2 to import XML (e.g. TrackMate, MaMuT, BigDataViewer) generate an exception with JDom 2.0.5. Example in MaMuT: java.lang.ExceptionInInitializerError at org.jdom2.input.SAXBuilder.<init>(SAXBuilder.java:338) at org.jdom2.input.SAXBuilder.<init>(SAXBuilder.java:221) at fiji.plugin.trackmate.io.TmXmlReader.<init>(TmXmlReader.java:168) at fiji.plugin.mamut.io.MamutXmlReader.<init>(MamutXmlReader.java:33) at fiji.plugin.mamut.LoadMamutAnnotationPlugin.load(LoadMamutAnnotationPlugin.java:68) at fiji.plugin.mamut.LoadMamutAnnotationPlugin.run(LoadMamutAnnotationPlugin.java:61) at ij.IJ.runUserPlugIn(IJ.java:212) at ij.IJ.runPlugIn(IJ.java:176) at ij.Executer.runCommand(Executer.java:132) at ij.Executer.run(Executer.java:65) at java.lang.Thread.run(Thread.java:745) Caused by: org.apache.xerces.xni.parser.XMLConfigurationException: http://apache.org/xml/features/allow-java-encodings at org.apache.xerces.impl.xs.XMLSchemaLoader.getFeature(Unknown Source) at org.apache.xerces.jaxp.validation.XMLSchemaFactory.propagateFeatures(Unknown Source) at org.apache.xerces.jaxp.validation.XMLSchemaFactory.newSchema(Unknown Source) at org.jdom2.input.sax.XMLReaders.<init>(XMLReaders.java:123) at org.jdom2.input.sax.XMLReaders.<clinit>(XMLReaders.java:95) ... 11 more It is apparently linked to creating a SAX parser with no args, as in: final SAXBuilder sb = new SAXBuilder(); The issue is referred here: http://comments.gmane.org/gmane.comp.java.jdom.general/4070 where it is suggested to specify a specific parser. However, updating JDom2 version to 2.0.6 fixes the problem and leave the parser choice to JDom2. This branch updates JDom2 version shipped in SciJava project from v2.0.5 to v2.0.6.
Member
|
Great! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently, some of the tools that rely on JDom2 to import XML (e.g. TrackMate & MaMuT) generate an exception with JDom 2.0.5.
Example in MaMuT:
Is is apparently linked to creating a SAX parser with no args, as in:
final SAXBuilder sb = new SAXBuilder();The issue is referred here:
http://comments.gmane.org/gmane.comp.java.jdom.general/4070
where it is suggested to specify a specific parser.
However, updating JDom2 version to 2.0.6 fixes the problem and leave the parser choice to JDom2.
This PR updates JDom2 version shipped in SciJava project from v2.0.5 to v2.0.6.