Tobias Erdle

Seems the build fetches an old CDI TCK: `[INFO] Downloading from jakarta-snapshots: https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/enterprise/cdi-tck-api/4.0.5/cdi-tck-api-4.0.5.pom` [see here](https://ci.eclipse.org/jakartaee-tck/job/10/job/jakarta-cdi-tck-glassfish-run-cert/org.glassfish$glassfish.cdi-tck/21/consoleFull) Those errors were fixed in CDI TCK 4.0.7, which was released after the PR stated...

I'm no expert in CDI TCK, so as far as I understood was this change only to improve the test assumption, not the expected result.

Thanks for opening the ticket. I remember we had this stacktrace before some time ago.I'll check the old issues later.

I just had a few minutes to upload the PoC: https://github.com/erdlet/poc-krazo-asset-controller I think a resource like this can be really helpful for "Jakarta MVC only" applications to get static assets...

After testing this a little bit I found a few topics that need investigation: - How to solve subdirectories? At the moment, the PoC can't handle paths like `/js/foobar/somescript.js` -...

> GlassFish seems to have a different resolving mechanism for WEB-INF/ files than This bug was fixed by GlassFish, so we can add this feature now and it should behave...

Hi @mthmulders, thanks a lot for testing and providing this detailed analysis. It'd be great when you vould provide your solution to Krazo, since we're a little bit short of...

We can find a up-to-date working example for Krazo on Tomcat here: https://github.com/mvc-toolbox/mvc-toolbox/blob/3d544396e564a197d81165851e4000ee38b8bdb5/showcase/pom.xml#L85-L178

Generally I like the idea and think we should add it, because it helps people using Krazo to add different ways of view resolution and us too, as we can...

> ... where a custom resolver can only provide a viewable for some controllers but should also be able to fall back to the default implementation. This reminds me of...