Primefaces custom stack menu upgrade#
Primefaces custom stack menu code#
Primefaces custom stack menu free#

For now, I've just commented out the parts of tests that used to do this.

I'm not sure if this is caused by the JSF core or the component library, but it remains an open issue. For some reason, performing file uploads and setting checkbox values works fine with MyFaces/Tomahawk, but not with Mojarra/PrimeFaces. We use Canoo WebTest to run integration tests on the UI in AppFuse. This seems to have happened before in previous releases and is currently an open issue.Ĭanoo WebTest doesn't work with fileUpload nor to set checkbox values WARNING: JSF1064: Unable to find or serve resource, images/ui-bg_highlight-hard_70_000000_1x100.png, from library, primefaces-bootstrap. 10:40:25 PM .resource.ResourceHandlerImpl logMissingResource The PrimeFaces Bootstrap theme 404s on some imagesĪfter integrating PrimeFaces' Bootstrap theme, the following error shows up in server logs.

For some reason, this doesn't work with PrimeFaces.

Below is the code I used successfully with MyFaces. It was hidden correctly when adding a user, but clicking on it to delete a user simply refreshes the page. The next thing I noticed was the Delete button didn't work when editing a user. I found the fix for this on Stack Overflow and added the following listener to my web.xml to solve it.Ĭonditionally rendering a button disables its click-ability : Application was not properly initialized at startup, could not find Factory: Īt $FactoryManager.getFactory(FactoryFinder.java:951)Īt (FactoryFinder.java:316)Īt .init(FacesServlet.java:302)Īt .ServletHolder.initServlet(ServletHolder.java:492)Īt .ServletHolder.doStart(ServletHolder.java:312) It worked fine in Tomcat but I got the following error in Jetty:

PrimeFaces resources served up at //* not foundĪn IllegalStateException on startup when using 'mvn jetty:run' The first issue I encountered was that I was unable to run the app in Jetty.

Canoo WebTest doesn't work with fileUpload nor to set checkbox values.

The PrimeFaces Bootstrap theme 404s on some images.

Conditionally rendering a button disables its click-ability.

An IllegalStateException on startup when using 'mvn jetty:run'.

While integrating these two frameworks, I ran into a number of issues. I hope the PrimeFaces developers fix this soon. It means that if you're using a JSF archetype, the PrimeFaces repo will be checked for artifacts first, causing an unnecessary slowdown in artifact resolution.

This is unfortunate since all of AppFuse's other dependencies can be found in Maven Central. The first thing I noticed when integrating PrimeFaces is you have to add a custom repository in order to get its artifacts via Maven.

Feel free to leave comments on ask questions in the review itself.

You can see all the changes I made (which include a Jetty plugin upgrade and some cleanup) in this Crucible review. Last week, I spent a few hours integrating Gilberto's changes into AppFuse's master branch. Shortly after the AppFuse 2.2.1 release in December, Gilberto Andrade contributed a sample project that used Mojarra (the JSF RI) and PrimeFaces instead of MyFaces and its Tomahawk components. Since PrimeFaces contains a Bootstrap theme, I hope this is a pleasant experience and my overall opinion of JSF improves. That's why I'll be integrating it (or merging your pull request) into the 2.3 release of AppFuse. there's a lot of folks praising JSF 2 (and PrimeFaces moreso). When describing my bias against JSF back in November, I wrote:

Primefaces custom stack menu code#

Primefaces custom stack menu free#

Primefaces custom stack menu upgrade#