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 210009 - net.sf.saxon.trans.XPathException: DOMSource cannot be processed: check that saxon9-dom.jar is on the classpath
Summary: net.sf.saxon.trans.XPathException: DOMSource cannot be processed: check that ...
Status: RESOLVED DUPLICATE of bug 208369
Alias: None
Product: platform
Classification: Unclassified
Component: Autoupdate (show other bugs)
Version: 7.2
Hardware: All All
: P3 normal (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-23 14:59 UTC by MackSix
Modified: 2012-05-31 15:36 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 186197


Attachments
stacktrace (665 bytes, text/plain)
2012-03-23 14:59 UTC, MackSix
Details

Note You need to log in before you can comment on or make changes to this bug.
Description MackSix 2012-03-23 14:59:48 UTC
Build: NetBeans IDE Dev (Build 201203230400)
VM: Java HotSpot(TM) Client VM, 22.1-b02, Java(TM) SE Runtime Environment, 1.7.0_03-b05
OS: Windows Vista

User Comments:
MackSix: Trying to install C/C++ Plugin.




Stacktrace: 
net.sf.saxon.trans.XPathException: DOMSource cannot be processed: check that saxon9-dom.jar is on the classpath
   at net.sf.saxon.event.Sender.send(Sender.java:251)
   at net.sf.saxon.IdentityTransformer.transform(IdentityTransformer.java:30)
   at org.netbeans.updater.XMLUtil.write(XMLUtil.java:146)
   at org.netbeans.updater.UpdateTracking$Module.write(UpdateTracking.java:773)
   at org.netbeans.updater.ModuleUpdater.unpack(ModuleUpdater.java:522)
   at org.netbeans.updater.ModuleUpdater.run(ModuleUpdater.java:142)
Comment 1 MackSix 2012-03-23 14:59:53 UTC
Created attachment 117169 [details]
stacktrace
Comment 2 Jiri Rechtacek 2012-03-26 09:09:27 UTC
Please, attach whole your messages.log. It seems you are using other XML parser than bundled one. Thanks
Comment 3 Jiri Rechtacek 2012-05-31 15:36:15 UTC

*** This bug has been marked as a duplicate of bug 208369 ***