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 52857 - ClassNotFoundException when adding a CVS profile
Summary: ClassNotFoundException when adding a CVS profile
Status: CLOSED DUPLICATE of bug 51945
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 4.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@platform
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-03 13:18 UTC by Roman Strobl
Modified: 2008-12-22 17:53 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Exception (6.29 KB, text/plain)
2005-01-03 13:18 UTC, Roman Strobl
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Strobl 2005-01-03 13:18:21 UTC
[Netbeans 200501021900; JDS R3; JDK 1.5.0_01]

The attached exception occurs when I try to add a
CVS profile. I fill in all required information
and click Finish. Then the profile is created but
an exception pops up as well.
Comment 1 Roman Strobl 2005-01-03 13:18:57 UTC
Created attachment 19435 [details]
Exception
Comment 2 Martin Entlicher 2005-01-03 14:15:42 UTC
Some problem in DOM impl.
Comment 3 Marian Mirilovic 2005-01-04 08:17:28 UTC
java.io.IOException: Unsupported DOM document implementation!
java.lang.ClassNotFoundException: org.apache.xml.serialize.XMLSerializer
	at
org.openide.xml.XMLUtilImpl.handleImplementationException(XMLUtilImpl.java:207)
	at org.openide.xml.XMLUtilImpl.write(XMLUtilImpl.java:175)
	at org.openide.xml.XMLUtil.write(XMLUtil.java:298)

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

Roman , 
do you use standard JDK installation without any additional patches ? 
It seems like you have something non standard on classpath ...
Comment 4 Roman Strobl 2005-01-04 10:25:02 UTC
I use standard JDK 1.5.0_01-b08. I've tried it today with new build
and userdir and it works fine. I've found out the problem is that I
had some of the modules turned off, when all of them are on it works fine.

For instance, I've disabled all webapps- and J2EE-related modules.
Then this exception pops up in Versioning manager. However when I
activate the Tomcat 5 server module the exception stops to occur. I
didn't find a better testcase than deactivating all webapps- and
J2EE-related modules. Several of the modules seem to solve the issue
after re-activating and thus it is not connected with a single module.

Comment 5 _ rkubacki 2005-02-17 12:22:59 UTC
This is just another consequence of issue #51945

*** This issue has been marked as a duplicate of 51945 ***
Comment 6 Roman Strobl 2005-07-08 09:22:45 UTC
Verified.