PrimeFaces on Quarkus made simple

PrimeFaces is a renowned open-source UI component library for JSF-based web applications. It provides an extensive set of rich, customizable UI components that simplify the process of building feature-rich and visually appealing user interfaces. In this article we will learn how to integrate its library in Quarkus applications.

This is the second round of article about runing PrimeFaces in the context of Jakarta EE applications. In the first article, we have showed how to deploy PrimeFaces on WildFly application Server: PrimeFaces with Jakarta EE 10 made simple

In terms of source code, we will not need to modify any aspect of our application. On the other hand, we will show the configuration changes required to run the application on a Quarkus 3 environment.

Configuring Quarkus for PrimeFaces

Firstly, we need to include PrimeFaces extension in our Quarkus project. This extension belongs to the Quarkiverse extensions, which contains experimental libraries which are not still part of the core Quarkus IO extensions:


Behind the hoods the above extension will fetch MyFaces as Jakarta Faces implementation:

[INFO] +- io.quarkiverse.primefaces:quarkus-primefaces:jar:3.13.3:compile
[INFO] |  +- org.apache.myfaces.core.extensions.quarkus:myfaces-quarkus:jar:4.0.1:compile
[INFO] |  |  +- org.apache.myfaces.core:myfaces-api:jar:4.0.1:compile
[INFO] |  |  +- org.apache.myfaces.core:myfaces-impl:jar:4.0.1:compile

The second focus point is the location of Web Content. Quarkus provides Web Content (static or dynamic) from the resources/META-INF/resources folder. Therefore, we will move our XHTML pages in that folder:

├── main
│   ├── docker
│   │   └── Dockerfile.native
│   ├── java
│   │   └── com
│   │       └── sample
│   │           ├── bean
│   │           │   └──
│   │           ├── model
│   │           │   └──
│   │           └── service
│   │               └──
│   └── resources
│       ├──
│       ├── import.sql
│       └── META-INF
│           ├── resources  <----------- Root Folder for Web Content
│           │   ├── accessibility.xhtml
│           │   ├── error.xhtml
│           │   ├── favicon.ico
│           │   ├── index.xhtml
│           │   ├── template
│           │   │   └── template.xhtml
│           │   └── viewExpired.xhtml
│           └── web.xml

Finally, you should be aware that Quarkus has no concept of handling multiple Web Applications and Contexts as an application server does. Therefore, your application will be available, by default, on the root Web Context (“/”). If you want to change the HTTP Root Path you can use the following setting:


Running the Quarkus PrimeFaces application

That being said, let’s run our first Quarkus application with PrimeFaces. For this purpose, you can download the application from here, which includes all the configuration changes:

Now run the application with:

mvn install quarkus:dev

Here is our PrimeFaces application which has turned into a Quarkus one:

primefaces with quarkus tutorial

Since our application is running in Quarkus Dev Mode, you can apply any change to it and see it on the User Interface without restarting it. For example, you could try changing the UI theme as follows:


Then, if you save the web.xml page and hit refresh you will see the UI theme to change instantly:

getting started with quarkus and primefaces


The combination of PrimeFaces and Quarkus presents a compelling solution for developers seeking to build modern web applications that excel in both user experience and performance. By mixing PrimeFaces’ rich UI components with Quarkus’ cloud-native and optimized capabilities, developers can create responsive, scalable, and efficient web interfaces that cater to today’s demanding user expectations.