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.
When the visual web tools preview modules are enabled, all JSP files disappear from my free-form web project trees. This occurs in both the projects and files views whether I use "package" or "tree" views. The folder in question *is* properly denoted as being a web pages folder in the free form web project. This is very easily seen. Fortunately disabling the visual web modules makes the JSPs reappear. Unfortunately, re-enabling them *immediately* makes all the JSPs disappear once again. I e-mailed to nbusers and radl@fss.cz replied that he'd done so already with the same problem and gotten no response. This is clearly reproducible.
Not only should the visual web modules not stop free-form web projects from functioning properly, but the visual web capabilities should be usable from free form projects. It took me hours to figure out how to do something approximating a normal web project's JSP compilation in a free-form project -- and this is still not quite right. Examples as to how to wire such things in -- or better yet auto-generation of such targets to ide-file-targets.xml is necessary.
I can't reproduce here! Could you please give us more details of how we can reproduece it? It may be caused by your project structure 'uses' the same identity as VWP but not complete.
I'm not *using* the Visual Web stuff in any way. This is just a simple free-form web project with a "src_web" sub-directory containing my web pages. I just installed it meaning to play with it at some point. I may have updated to the latest beta thereof as well, which could be the issue. [How can I dump my module versions for you?] I will attach a gutted version of my project that should shed some light on its arrangement.
Created attachment 35737 [details] Gutted version of free form project causing issues
I tried your project and all the JSP files are visible from both the Projects and Files views! Is that possible you have other NetBeans plugings that conflict with VWP? Is your installation just NetBeans 5.5 FCS + VWP Pack?
Created attachment 35738 [details] Projects view shows all JSP files as I tested
Created attachment 35739 [details] Files view shows all JSP files as I tested
This was fixed on 2006/10/11 (IN=101766). You should find the following exceptions in message.log, right? java.io.IOException: java.lang.NullPointerException at org.openide.loaders.DataLoader.findDataObject(DataLoader.java:379) at org.openide.loaders.DataLoaderPool.findDataObject(DataLoaderPool.java:408) at org.openide.loaders.FolderList.createBoth(FolderList.java:707) at org.openide.loaders.FolderList.getObjects(FolderList.java:518) at org.openide.loaders.FolderList.access$200(FolderList.java:56) at org.openide.loaders.FolderList$ListTask.run(FolderList.java:886) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:499) [catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:932) Caused by: java.lang.NullPointerException at com.sun.rave.project.jsf.api.JsfProjectUtils.getDocumentRoot(JsfProjectUtils.java:391) at com.sun.rave.project.jsf.api.JsfProjectUtils.getBasePathForJsp(JsfProjectUtils.java:599) at com.sun.rave.project.jsf.api.JsfProjectUtils.getJavaForJsp(JsfProjectUtils.java:505) at com.sun.rave.project.jsfloader.Utils.findJavaForJsp(Utils.java:46) at com.sun.rave.project.jsfloader.JsfJspDataLoader.findPrimaryFile(JsfJspDataLoader.java:82) at org.openide.loaders.MultiFileLoader.findPrimaryFileImpl(MultiFileLoader.java:268) at org.openide.loaders.MultiFileLoader.handleFindDataObject(MultiFileLoader.java:71) at org.openide.loaders.DataObjectPool.handleFindDataObject(DataObjectPool.java:129) at org.openide.loaders.DataLoader.findDataObject(DataLoader.java:364) ... 7 more
Fixed in trunk.
That exception looks familiar, yes. I would have included it in the bug report but I lost the exception (inexcusable, I know). I'm glad to hear this has been addressed. I'm not concerned about the interim -- I just wanted to make sure this didn't stay broken in future visual web module updates and/or the final release.