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.
Hi, I have a UML project that generated reports correctly until a few days ago. Now when I generate a report from the project, NB uses up about 600 Mb of memory and the report generated is faulty. One thing that changed in NB's behavior is that at the time report generation was working properly, the browser was started after the report was generated, this is no longer the case. The error that I get when I open the index.html myself is that the frames are empty, stating that the various pages to be displayed in the different frames do not exist. Which is true. When I do a dir in the report directory I get the following output: 08/17/2007 09:48 AM <DIR> . 08/17/2007 09:48 AM <DIR> .. 08/17/2007 10:51 AM 7,910 behaviour.js 08/17/2007 10:51 AM 6,093 DCE56DDC878832E13382D8E88CE0A55E559-frame .html 08/17/2007 10:51 AM 11,439 DCE56DDC878832E13382D8E88CE0A55E559.html 08/17/2007 09:48 AM 0 DCE7064E08D905ABB008424B57FE0B80157.html 08/17/2007 10:54 AM 0 DCE9E66C1D429BEE8F0E6023828A714DBE2.html 08/17/2007 10:51 AM 5,117 help.html 08/17/2007 09:48 AM <DIR> images 08/17/2007 10:51 AM 1,167 index.html 08/17/2007 10:51 AM <DIR> PluginServer 08/17/2007 10:51 AM 3,570 stylesheet.css 08/17/2007 10:51 AM 7,384 zoom.js 9 File(s) 42,680 bytes 4 Dir(s) 7,926,505,472 bytes free I have tried deleting the report directory and generate from scratch but that gave the same results. I tried this in the NB6M10 build as well as the 200708100000 build, with the same result. Other UML projects generate proper reports. In the log file an NPE is present on the reporting functionality, but no hint as to where something in my project went wrong. Iwan
Created attachment 46780 [details] The related log file
The log indicates there is an element in your project whose owning package is null, which should not happen in normal situation as the top level package defaults to project itself. It would be helpful if you can find a way to reproduce the steps that lead to the invalid element. Would it be possible to attach your project for debugging?
This is related to issue 114310. If original project is not loaded imported elements cannot be properly resolved, the null owning package caused runtime exception. With fix to issue 115766, user should be able to identify those failed elements and correct the model accordingly.
Hi, I always have all projects open, yet I don't get a proper report generated. Iwan
using the instrumented trunk build 200710010405. I still see the same exception below and report not generated correctly if I closed the referenced uml project to generate the model report. The diagram is being modified based on the changes in the model SEVERE [org.netbeans.modules.uml.reporting.dataobjects.ElementDataObject]: Class - pkgClass1 java.lang.NullPointerException at org.netbeans.modules.uml.reporting.dataobjects.ElementDataObject.getOwningPackageName(ElementDataObject.java:364) [catch] at org.netbeans.modules.uml.reporting.dataobjects.ClassData.toReport(ClassData.java:567) at org.netbeans.modules.uml.reporting.ReportTask.createFileForElement(ReportTask.java:391) at org.netbeans.modules.uml.reporting.ReportTask.loadDataElement(ReportTask.java:310) at org.netbeans.modules.uml.reporting.ReportTask.processChildren(ReportTask.java:342) at org.netbeans.modules.uml.reporting.ReportTask.loadDataElement(ReportTask.java:311) at org.netbeans.modules.uml.reporting.ReportTask.processChildren(ReportTask.java:342) at org.netbeans.modules.uml.reporting.ReportTask.loadDataElement(ReportTask.java:311) at org.netbeans.modules.uml.reporting.ReportTask.generateReport(ReportTask.java:201) at org.netbeans.modules.uml.reporting.ReportTask.run(ReportTask.java:181) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:561) at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:986)
Peter, can you verify it again with the latest build?
Just verified in trunk build 20071101142452. Here's the result. If the referenced project is opened at report generation, everything is working correctly. However, if I closed the referenced project where imported elements exist, I now got the following exception from the ide logfile and exception popup dialog as well. WARNING [org.netbeans.modules.uml.reporting.ReportTask]: Invalid Item: Generalization|Super Exception SEVERE [org.netbeans.modules.uml.reporting.dataobjects.ElementDataObject]: Generating report for UMLProject1 ... java.lang.NullPointerException at org.netbeans.modules.uml.reporting.ReportTask.processChildren(ReportTask.java:320) at org.netbeans.modules.uml.reporting.ReportTask.loadDataElement(ReportTask.java:312) at org.netbeans.modules.uml.reporting.ReportTask.processChildren(ReportTask.java:343) at org.netbeans.modules.uml.reporting.ReportTask.loadDataElement(ReportTask.java:312) at org.netbeans.modules.uml.reporting.ReportTask.processChildren(ReportTask.java:343) at org.netbeans.modules.uml.reporting.ReportTask.loadDataElement(ReportTask.java:312) at org.netbeans.modules.uml.reporting.ReportTask.processChildren(ReportTask.java:343) at org.netbeans.modules.uml.reporting.ReportTask.loadDataElement(ReportTask.java:312) at org.netbeans.modules.uml.reporting.ReportTask.processChildren(ReportTask.java:343) at org.netbeans.modules.uml.reporting.ReportTask.loadDataElement(ReportTask.java:312) at org.netbeans.modules.uml.reporting.ReportTask.processChildren(ReportTask.java:343) at org.netbeans.modules.uml.reporting.ReportTask.loadDataElement(ReportTask.java:312) at org.netbeans.modules.uml.reporting.ReportTask.processChildren(ReportTask.java:343) at org.netbeans.modules.uml.reporting.ReportTask.loadDataElement(ReportTask.java:312) at org.netbeans.modules.uml.reporting.ReportTask.generateReport(ReportTask.java:202) [catch] at org.netbeans.modules.uml.reporting.ReportTask.run(ReportTask.java:182) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:561) at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:986)
Removing obsolete assignments. Bugs will be reassigned for M2.
reporting feature has not yet been implemented in 6.5.