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 178317 - java.io.IOException: cvc-complex-type.2.4.b: The content of element 'data' is not complete. One of '{"http://www.netbeans.org/ns/j2se-project/3":minimum-ant-version, "http://www.netbeans.org/ns/j2se-p
Summary: java.io.IOException: cvc-complex-type.2.4.b: The content of element 'data' is...
Status: RESOLVED FIXED
Alias: None
Product: projects
Classification: Unclassified
Component: Ant Project (show other bugs)
Version: 6.x
Hardware: All All
: P1 normal with 1 vote (vote)
Assignee: Jesse Glick
URL:
Keywords:
: 187971 189188 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-12-08 12:14 UTC by ievans
Modified: 2010-08-04 12:18 UTC (History)
18 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 161146

Attachments
stacktrace (1.07 KB, text/plain)
2009-12-08 12:14 UTC, ievans 		Details
stacktrace (824 bytes, text/plain)
2010-01-16 15:56 UTC, franci 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ievans 2009-12-08 12:14:28 UTC 
Build: NetBeans IDE 6.8 RC2 (Build 200912022200)
VM: Java HotSpot(TM) Client VM, 14.3-b01, Java(TM) SE Runtime Environment, 1.6.0_17-b04
OS: Windows XP, 5.1, x86

User Comments:
ievans: Opening a Java project.

GUEST: I was renaming the project while the project was runnig

GUEST: copying a maven project



Stacktrace: 
java.io.IOException: cvc-complex-type.2.4.b: The content of element 'data' is not complete. One of '{"http://www.netbeans.org/ns/j2se-project/3":minimum-ant-version, "http://www.netbeans.org/ns/j2se-project/3":explicit-platform, "http://www.netbeans.org/ns/j2se-project/3":web-service-clients, "http://www.netbeans.org/ns/j2se-project/3":source-roots}' is expected.
   at org.netbeans.modules.project.uiapi.DefaultProjectOperationsImplementation$4$2.run(DefaultProjectOperationsImplementation.java:379)
   at org.openide.filesystems.EventControl.runAtomicAction(EventControl.java:122)
   at org.openide.filesystems.FileSystem.runAtomicAction(FileSystem.java:539)
   at org.netbeans.modules.project.uiapi.DefaultProjectOperationsImplementation$4.execute(DefaultProjectOperationsImplementation.java:374)
   at org.netbeans.modules.project.uiapi.DefaultProjectOperationsImplementation$6$1.run(DefaultProjectOperationsImplementation.java:670)
   at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:602)
Comment 1 ievans 2009-12-08 12:14:32 UTC 
Created attachment 92298 [details]
stacktrace
Comment 2 franci 2010-01-16 15:56:23 UTC 
Created attachment 93350 [details]
stacktrace

just renaming a java project with .c .h and .cc files in src directory
Comment 3 jahogie 2010-01-26 14:12:02 UTC 
I was renaming a list of tiny projects and/or 
opening another one intending to rename it also.
Comment 4 Exceptions Reporter 2010-02-05 10:14:46 UTC 
This bug already has 150 duplicates 
see http://statistics.netbeans.org/exceptions/detail.do?id=161146
Comment 5 Jesse Glick 2010-02-05 11:39:03 UTC 
This error means that project.xml is malformed. Is it known to be reproducible somehow?
Comment 6 Milos Kleint 2010-02-05 13:33:11 UTC 
well, it looks to me like a lot of the reports are just random IO errors happening during the project operations. Maybe just a misplaced exception logging which should be a proper UI?
Comment 7 Jesse Glick 2010-02-05 17:04:28 UTC 
Not actually fixed at all, but marking fixed is the only way to get the exception reporter to stop attaching hundreds of duplicates. Due to poor coding style, the original stack traces from a variety of unrelated exceptions were being discarded and a generic IOException thrown from a few places in DefaultProjectOperationsImplementation. Many of the duplicates have common messages such as "String index out of range: -1", and the body of the try statement calls into complex SPI implementations in project types, so it is hardly possible to guess what code was originally at fault. core-main #44d6ec7cafac retains the original stack trace in the wrapper exception, so if the errors are thrown from a build containing this fix, the exception reporter ought to open fresh specific bugs.


6.8 patch backport tip: for JDK 5 compatibility, replace

  throw new IOException(x);

with

  throw (IOException) new IOException(x.toString()).initCause(x);
Comment 8 Jesse Glick 2010-06-23 13:24:37 UTC 
*** Bug 187971 has been marked as a duplicate of this bug. ***
Comment 9 Jesse Glick 2010-08-04 12:18:42 UTC 
*** Bug 189188 has been marked as a duplicate of this bug. ***