Ondro Mihályi

Can't we just create an Arquillian extension that repackages EAR into WAR (where it makes sense)? Where it doesn't make sense (like when the test relies on application.xml), just exclude...

What I would expect as a developer from the client API: If Rest Client is built **without a CDI container**, e.g. from a `main` method: * Providers are retrieved from...

Hi, my view on this is sort of mixed but practical. I've always had problems with `@Context` injection, which works completely on its own and doesn't even rely on plain...

@mkarg, @chkal > Agreed. It would be very beneficial to have everything in one place. This seems tempting but it doesn't work well if tests should also cover integration of...

As an example, MicroProfile currently uses the approach of having the TCK in the API repository. And we're hitting the issue of how to write tests that ensure that multiple...

According to the thread dumps, the source of inefficiency seems to be the `MultiReleaseResource` class. In the [versionedEntry](https://github.com/piranhacloud/piranha/blob/current/resource/impl/src/main/java/cloud/piranha/resource/impl/MultiReleaseResource.java#L131C17-L131C31) method, it iterates over a list of Java versions, and for each...

Another optimization is to unpack JAR files into a temp folder and then load resources from that folder. This would optimize time to load resources for any JAR file, even...

Another optimization, again for any JAR file, could be to use multiple (virtual) threads to read from a JAR file. Each JAR file can be read by a different thread,...

I didn't have time to investigate how to fix this. I'd like to get to this when I have some time.

I think this is already resolved in Faces 4.0, with the following simplified namespaces: * `jakarta.faces.composite`, e.g. xmlns:ez="jakarta.faces.composite/ezcomp" * `jakarta.faces.html` * `jakarta.faces.core` * `jakarta.faces.facelets` * `jakarta.faces.passthrough` * `jakarta.tags.core` * `jakarta.tags.functions`...