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. Create new Web Application. 2. Choose Apache Tomcat 5.0.15 & JavaEE 7 Web 3. Choose JavaServer Faces 4. Click Components Tab and then click the "More..." button. 5. Wait a bit until default PrimeFaces 5.0 library is detected. 6. Click "Create Library" button. 7. Name PrimeFaces 5.1 and add primefaces-5.1.jar 8. Wait a bit until PrimeFaces libraries are detected. Results: PrimeFaces 5.1 is not detected and is not shown in the PrimeFaces Libraries ComboBox. Only PrimeFaces 5.0 is shown. Expected: PrimeFaces 5.1 & PrimeFaces 5.0 both show in ComboBox. The Library is added correctly and shows in Tools>>Libraries. Product Version: NetBeans IDE 8.0.2 (Build 201411181905) Java: 1.8.0_25; Java HotSpot(TM) 64-Bit Server VM 25.25-b02 Runtime: Java(TM) SE Runtime Environment 1.8.0_25-b18 System: Windows 7 version 6.1 running on amd64; UTF8; en_US (nb)
In step 2 of Comment 0 should be Tomcat 8.0.15
Same problem running NB 8.0.2 in linux Mint w/Glassfish; when PrimeFaces is selected as the JSF component, the message JSF library PrimeFaces not set up properly: Searching valid Primefaces library. Please wait... is shown in red for some time then eventually goes away. Clicking the "More" button for Primefaces only shows the 5.0 library even though I have installed 5.1.
Please, correct that, if you just remove and add the same jar the problem still occurs.
(In reply to erickdeoliveiraleal from comment #3) > Please, correct that, if you just remove and add the same jar the problem > still occurs. Please do not change priorities on bug reports until you review and understand the bug priority guidelines. Thank you. http://wiki.netbeans.org/BugPriorityGuidelines
The bug is independent of the target application server of project (checked for Tomcat, GlassFish, JBoss). The bug is also independent of the target PrimeFaces release (checked with 5.2 and 5.3 releases). Remark: all provided library names comply with the format displayed in Project properties/Frameworks/Components/PrimeFaces more...
(In reply to Fred_Vinet from comment #5) Please don't change the version of NetBeans a bug was originally reported for. It is assumed the issue is still valid in all versions of NetBeans after the reported version unless the bug is marked as fixed. If you like, you may add a comment that is it still valid in your version, but it it not necessary.
For anyone else who stumbles across this ... Here is a work-around that I am using for Netbeans 8.1 and Primefaces 6.0. 1. Create the 6.0 library in the Frameworks / JSF / Components / PrimeFaces properties box. It will not be recognized by the dialog, but the library is created. 2. Select 5.0 and close the dialog. 3. Open the project's Libraries tab. 4. Find and remove PrimeFaces 5.0 5. Add Library -> PrimeFaces 6.0 6. I downloaded and added atmosphere 2.4.3 I can't vouch for whether or not all of the various Netbeans PrimeFaces features will work, but I'll discover that as I continue!
Not a NetBeans issue, but a follow up to the above. When using Atmosphere 2.4.x with PrimeFaces 6.0 (required dependency for websockets), in certain server configurations the websocket component fails to deploy. I had the problem in Payara but not GlassFish. GlassFish has other issues. YMMV. https://github.com/Atmosphere/atmosphere/issues/2104 : Related to the way atmosphere and jsr356 are setup for 2.4.x. There is an option to go back to the 2.3.x behavior (see #2104). There is a new init parameter org.atmosphere.suppressDetectingJSR356 that can be set to true to suppress 2.4.x's jsr356 detection behavior. I used : <init-param> <param-name>org.atmosphere.websocket.suppressJSR356</param-name> <param-value>true</param-value> </init-param> Everything that I use is working, but I am primarily working on legacy code. YMMV.