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.
1. Register a build of the WebLogic developer web profile 2. Start up the server 3. Create a Java EE 6 application with WebLogic target, on the frameworks panel select JSF (the wizard offers JSF 2.0 implementation as a Server Library, which is probably correct). Problem 1: After the project is created, it is badged as erroneous. The IDE does not offer to deploy the JSF implementation to the server, and there is no JSF library under the Libraries node. 4. You can then choose Resolve Server Library Problem in the popup menu of the project and confirm the dialog - this resolves the problem and the project can be successfully deployed. Problem 2: After this step, JSF is still not visible under Libraries (this may be related to bug 197875)
Martin, can you please take a look? Thanks.
Problem 1: So after brutal debugging I find out that the issue was raised by fixing issue #197802. Finally the issue seems to be related to: a) projectui module - doesn't use first modal DialogDescriptor as a leaf b) core.windows module - doesn't reflect isLeaf() for NotifyDescriptor which is created by BrokenServerLibrarySupport.fixServerLibraries() After discussion with JardaT I created new issue #199083 for that and provided there some patch for fixing that. BTW, this problem is not related just to this one dialog but to all our Broken*Support dialogs and has to be probably fixed for NB701. After fixing this problem it looked to be working well again. Problem 2: I think that it's all right. If you use server library the library isn't added into project libraries. Try the same use case for GF, it will work in the same way.
This is a blocker that needs to be fixed in 7.0.1 -> P2.
Sorry, you are right that Problem 2 is not really a problem. What I should have written is: Problem 3: NetBeans still treats JSF as a "server library" on WebLogic DWP, however in reality this library is "built-in" in DWP (from what I heard). So there is no need to deploy the library to the server, create a library-ref element in weblogic.xml etc. This stuff should be streamlined and simplified.
We should not display the server library in the wizard to simplify things. However all the machinery has to preserved in order to support legacy projects which uses the server lib approach - if I understand that correctly this is the reason why there is such fake server lib in DWP.
Created attachment 108788 [details] suggested solution Martin, it would great if you could verify the solution.
Not sure about the sense of your defensive check on size. Anyway reviewed and verified, looks really well. I think that you can feel free to integrate it.
Fixed in web-main 2f09f02c4928.
Integrated into 'main-golden' Changeset: http://hg.netbeans.org/main-golden/rev/2f09f02c4928 User: phejl@netbeans.org Log: #197891 Problem setting up JSF on WebLogic developer web profile
Integrated into 'releases' Changeset: http://hg.netbeans.org/releases/rev/e225c9e07847 User: phejl@netbeans.org Log: #197891 Problem setting up JSF on WebLogic developer web profile