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 154110 - visual web jsf design page don't show up
Summary: visual web jsf design page don't show up
Status: NEW
Alias: None
Product: third-party
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 6.x
Hardware: Other Windows XP
: P3 blocker (vote)
Assignee: issues@third-party
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-28 17:42 UTC by umair_naqvi
Modified: 2008-12-01 21:38 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
stack trace (2.39 KB, text/plain)
2008-11-28 17:43 UTC, umair_naqvi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description umair_naqvi 2008-11-28 17:42:07 UTC
I've just started Netbeans 6.5 RC2 and started a new visual web jsf project and instead of the design page an 
exception occured. It is a continuous problem and design page is not showing up. I've downloaded the basic ide and 
then the plugin for web and jsf. Below find the stack trace
Regards
umair_naqvi
umair_naqvi@yahoo.com

java.lang.NullPointerException
	at org.netbeans.modules.visualweb.designer.markup.RaveDocumentBuilderFactory.createDocumentBuilder
(RaveDocumentBuilderFactory.java:146)
	at org.netbeans.modules.visualweb.designer.markup.RaveDocumentBuilderFactory.newDocumentBuilder
(RaveDocumentBuilderFactory.java:127)
	at org.netbeans.modules.visualweb.designer.markup.MarkupServiceImpl.createRaveSourceDocumentBuilder
(MarkupServiceImpl.java:338)
	at org.netbeans.modules.visualweb.api.designer.markup.MarkupService.createRaveSourceDocumentBuilder
(MarkupService.java:235)
	at org.netbeans.modules.visualweb.insync.markup.MarkupUnit.parseDom(MarkupUnit.java:348)
	at org.netbeans.modules.visualweb.insync.markup.MarkupUnit.read(MarkupUnit.java:502)
	at org.netbeans.modules.visualweb.insync.SourceUnit.sync(SourceUnit.java:552)
	at org.netbeans.modules.visualweb.insync.faces.FacesPageUnit.syncSubUnits(FacesPageUnit.java:257)
	at org.netbeans.modules.visualweb.insync.beans.BeansUnit.sync(BeansUnit.java:205)
	at org.netbeans.modules.visualweb.insync.live.LiveUnitWrapper.sync(LiveUnitWrapper.java:152)
	at org.netbeans.modules.visualweb.insync.models.FacesModel.syncImpl(FacesModel.java:1091)
	at org.netbeans.modules.visualweb.insync.Model.sync(Model.java:219)
	at org.netbeans.modules.visualweb.insync.ModelSet.syncAll(ModelSet.java:752)
	at org.netbeans.modules.visualweb.insync.models.FacesModelSet.syncAll(FacesModelSet.java:1486)
	at org.netbeans.modules.visualweb.insync.models.FacesModelSet.doModeling(FacesModelSet.java:537)
	at org.netbeans.modules.visualweb.insync.models.FacesModelSet.<init>(FacesModelSet.java:422)
Caused: java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
	at org.netbeans.modules.visualweb.insync.ModelSet.createInstance(ModelSet.java:265)
Caused: java.lang.RuntimeException
	at org.netbeans.modules.visualweb.insync.ModelSet.createInstance(ModelSet.java:269)
	at org.netbeans.modules.visualweb.insync.ModelSet.getInstance(ModelSet.java:250)
	at org.netbeans.modules.visualweb.insync.ModelSet$1.run(ModelSet.java:217)
[catch] at java.lang.Thread.run(Thread.java:619)
Comment 1 umair_naqvi 2008-11-28 17:43:48 UTC
Created attachment 74283 [details]
stack trace
Comment 2 Peter Zavadsky 2008-12-01 21:38:11 UTC
I assume (this appears here too often), it is again the issue with iReport module, which breaks the NB library classes
to be loaded (, please, check you have the iReport module installed).

In order to get the VW (and potentionally other modules using the mentioned NB library modules) to work, you need to
disable the iReport module.

In any case, passing there to get the iReport module fixed.