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.
There is new release of Primefaces - 5.1 which we should bundle into the next NetBeans version. This should cover upgrade of the bundled library, updated version numbers within PF support and updated generation features to keep them working and up-to-date. http://blog.primefaces.org/?p=3302
Can we please make it PrimeFaces 5.2? http://blog.primefaces.org/?p=3491
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. The library is created, but will *not* be recognized by the dialog. 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 for websockets (2.5 and up do not work). When using Atmosphere 2.4.x with PrimeFaces 6.0 (required dependency for websockets), in certain server configurations the websocket component fails to deploy. 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 had the problem in Payara but not GlassFish. GlassFish has other issues. I added the following to my web.xml : <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. I can't vouch for whether or not all of the various Netbeans PrimeFaces features will work.