Quinoa URL not available in prod-mode

[nimo23]

I have a Jakarta Faces app within src/main/resources:

and a Quinoa web app (based on Vite) within src/main/webui.
The vite.config.ts:

export default defineConfig({
    // application is deployed to the root domain
    base: '/',
    plugins: [react(), tsconfigPaths()],
    server: {
	port: 5173
    },
})

and the scripts in package.json:

"scripts": {
	"dev": "vite",
	"build": "tsc -b && vite build",
	"preview": "vite preview"
},

In dev-mode, it works well:

• Going to localhost:8080/index.xthml (note the suffix xhtml) will serve the jakarta faces app.
• Going to localhost:8080/index.html (note the suffix html) will serve the web app provided by quinoa.

However, when building the Quarkus app (with mvn clean package), the web app provided by Quinoa is no longer available at the specified URL. If you go to localhost:8080/index.html (or localhost:8080/index.xthml), the Jakarta Faces app will be deployed. However, I want the same URL behavior as when running in dev-mode, i.e. going to index.html should serve the web app provided by Quinoa and going to to index.xhtml, the Jakarta Faces app should be served.

My Quinoa settings in application.properties:

quarkus.http.port=8080
quarkus.http.enable-compression=true
quarkus.quinoa.enable-spa-routing=true

The following assumption made in https://docs.quarkiverse.io/quarkus-quinoa/dev/index.html is also somewhat irritating to me:

With Quinoa, you don’t need to manually copy the files to META-INF/resources. Quinoa has its own system and will provide another Vert.x route for it. If you have conflicting files with META-INF/resources, Quinoa will have priority over them.

This means that Quinoa's webui directory takes precedence over the contents of META-INF/resources, but in the case described above it seems that META-INF/resources takes precedence in prod mode. However, both are provided in dev-mode, which is what I want.

I guess I need a custom configuration to make it also work in prod-mode, i.e. serve Quinoa web app when going to localhost:8080/index.html, and serve Jakarta web app when going to localhost:8080/index.xhtml.
But what configuration do I have to do?

[melloware]

i am not sure i would try and combine these two things or you should serve your quinoa app at a different location. I am actually surprised it works in Dev Mode

[melloware]

I am pretty sure that is the issue is MyFaces Servlet is intercepting the requests BEFORE Quinoa gets them.
Reproducer:
quinoa-faces.zip

Works fine in Dev mode but if you run..

mvn clean package -Dquarkus.package.jar.type=uber-jar
java -jar target/quinoa-faces-runner.jar

So in dev mode you can go to

http://localhost:8080 -> Faces APP
http://localhost:8080/quinoa -> Quinoa App

but in PROD mode if you do...

http://localhost:8080 -> Faces APP
http://localhost:8080/quinoa -> 404 Page not found intercepted by JSF Error handler

[nimo23]

I am pretty sure that is the issue is MyFaces Servlet is intercepting the requests BEFORE Quinoa gets them.

If it's not a bug on quarkus-myfaces, then it would be good if we could specify an exclusion pattern, so that quarkus-myfaces knows what to ignore, for example:

// with this setting, quarkus-faces does not handle html files 
// (But I don't know how Faces Servlet handles CSS, JS, etc. 
// that should belong to the Quinoa webapp..
quarkus.myfaces.ignore.pattern=*.html

or

// quarkus-faces does not handle content within the react directory
quarkus.myfaces.ignore.dir=/react

A better solution would be to not need such settings. I think quarkus-myfaces is doing a switch in prod-mode that results in this behavior. Maybe we can switch it back manually. But what settings are they and is it safe to switch it back?

[melloware]

It could also be a VertX ordering where in Dev Mode VertX orders Quinoa higher and in Prod Mode its ordering MyFaces higher.

[nimo23]

It could also be a VertX ordering where in Dev Mode VertX orders Quinoa higher and in Prod Mode its ordering MyFaces higher.

Yes, I think so too. For example, with the following setting in application.properties:

quarkus.swagger-ui.always-include=true

the html pages of the swagger-ui can also be accessed in prod-mode (i.e. no faces servlet, which has priority here).

[melloware]

might need @ia3andy to chime in here.