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.
My J2EE application consists of one ejb module and one web module. I have added the glassfish appserv.jar library to the web module because I need to make use of the ProgrammaticLogin class that comes with this library. When I add the library to my project, it breaks the visual editor for JSP Pages and JSP Page-Fragments. When I delete the library from my project, I find the editor is working again. Weird, huh!?
Created attachment 61222 [details] this is the exception thrown by glassfish
a colleague of mine found out that adding two other glassfish libraries, namely "appserv-deployment-client.jar" and "appserv-ext.jar" resolves the problem. But still, the netbeans visual jsf editor should work no matter how messy my project's libraries are!!
Where those libraries simply missing in your project and you resolved it, i.e. is it non issue? Or did you expect those to be loaded automatically? Please, explain. Thanks.
> Where those libraries simply missing in your project and you resolved it Yes, these libraries were missing in my project. I did not see it at once because I did not get any errors or warnings. I don't know how my colleague found out that we had missing references, but anyhow, he resolved them and things started working again. > i.e. is it non issue? It is an issue. It would be a non-issue if I was talking about getting compile errors (you've got a point there: I should not be surprised if a project with missing libraries does not want to compile!). But I am not talking about compile errors (which I think I did not get anyway), but about the Visual JSF Editor that for some reason stopped working. My point is: The netbeans visual jsf editor should work no matter how messy my project's libraries are!! It should be able to open JSF files even if the project has missing libraries. (If this should not be possible for some reason, the editor should not throw an ugly stack trace, that would be my lowest expectation) > Or did you expect those [libraries] to be loaded automatically? No. I knew I had to manually add the glassfish libraries to my project in order to use the ProgrammaticLogin class. I have to say, though, that I cannot now try to reproduce the problem because the project is finished and I am now working on a computer without Netbeans. Btw, we ended up not using the ProgrammaticLogin class which we never quite got to work but instead used a JDBC Realm.
The visual editor is not working because of the compile time errors. Because of those the model can't be created, thus there nothing to be shown in the visual editor. I understand that you would like to get improvement from that point of view. That despite the errors, there would be built at least some tree, and instead of the nodes, which are not created due to those errors, to show some error boxes. That is relevant demand. Unfortunately the current implementation doesn't provide such model, so the visual designer can't show anything. In any case the rest of the issue should be OK, therefore I change this to RFE. Thanks.