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.
Recent jsfsupport change caused regression of reading Creator 2 portlet projects. I got the following error and the designer showing "Loading, please wait...". SEVERE [global] java.util.NoSuchElementException at java.net.URLClassLoader$3.nextElement(URLClassLoader.java:407) at java.net.URLClassLoader$3.nextElement(URLClassLoader.java:382) at org.netbeans.modules.visualweb.jsfsupport.container.JsfTagSupport.initialize(JsfTagSupport.java:64) at org.netbeans.modules.visualweb.jsfsupport.container.FacesContainer.initialize(FacesContainer.java:214) at org.netbeans.modules.visualweb.jsfsupport.container.FacesContainer.<init>(FacesContainer.java:132) at org.netbeans.modules.visualweb.insync.models.FacesModelSet.getFacesContainer(FacesModelSet.java:497) at org.netbeans.modules.visualweb.insync.models.FacesModelSet.<init>(FacesModelSet.java:403) 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:257) Caused: java.lang.RuntimeException at org.netbeans.modules.visualweb.insync.ModelSet.createInstance(ModelSet.java:261) at org.netbeans.modules.visualweb.insync.ModelSet.getInstance(ModelSet.java:242) at org.netbeans.modules.visualweb.insync.ModelSet$1.run(ModelSet.java:209) [catch] at java.lang.Thread.run(Thread.java:619)
Created attachment 54890 [details] Creator 2 Portlet project follow the tutorial
When opening the attached project, you will get unresolved server red badge. Just select any of available server to resolve the red badge. Then opening the "PortletPage1.jsp", you will see the exception and the empty designer.
Please fix this as soon as possible because the VisualWeb Portlet support is now under critical release schedule! Thanks!
Po-Ting, when I opened the project, I got two unresolved reference portlet-runtime & jsf-portlet-runtime. How do I solve it?
Anyway, I've fixed the problem and checked in the code. I was able to open the page though, with out resolving the reference. IDE:------------------------------------------------- IDE: [1/9/08 5:52 PM] Committing "container" started cvs server: scheduling file `JsfTagSupportException.java' for addition cvs server: use 'cvs commit' to add this file permanently Checking in FacesContainer.java; /cvs/visualweb/jsfsupport/src/org/netbeans/modules/visualweb/jsfsupport/container/FacesContainer.java,v <-- FacesContainer.java new revision: 1.7; previous revision: 1.6 done RCS file: /cvs/visualweb/jsfsupport/src/org/netbeans/modules/visualweb/jsfsupport/container/JsfTagSupportException.java,v done Checking in JsfTagSupportException.java; /cvs/visualweb/jsfsupport/src/org/netbeans/modules/visualweb/jsfsupport/container/JsfTagSupportException.java,v <-- JsfTagSupportException.java initial revision: 1.1 done Checking in JsfTagSupport.java; /cvs/visualweb/jsfsupport/src/org/netbeans/modules/visualweb/jsfsupport/container/JsfTagSupport.java,v <-- JsfTagSupport.java new revision: 1.5; previous revision: 1.4 done Checking in Bundle.properties; /cvs/visualweb/jsfsupport/src/org/netbeans/modules/visualweb/jsfsupport/container/Bundle.properties,v <-- Bundle.properties new revision: 1.5; previous revision: 1.4 done IDE: [1/9/08 5:52 PM] Committing "container" finished BTW, the problem related to <p:portletPage> still exists. We need a test project to test that fix in the insync side.
Yes, those 2 libraries are just for runtime. You don't need to resolve them for designtime. Thanks! I will try it asap. And I will provide an example project for insync soon.
Verified.