Jan Bartel

@jkoch70 were you able to give the `TinyBundles` approach a go?

Jetty 12 EE10 corresponds to the Servlet 6 specification, and all classes that were `javax.servlet` changed to `jakarta.servlet` so you will need to modify your web app accordingly. Or alternatively...

@joakime @ovidijusnortal so it appears that this is a Spring issue, not a Jetty issue, thus can we close this issue?

@markt-asf any comments on the challenge to the `flushBufferTest`?

It sounds more like you want to be able to enable/disable _modules_ per webapp rather than just _configurations_? Disabling only a _configuration_ does not prevent the classes going onto the...

It seems OpenWebBeans has been ported to the jakarta namespace, however as yet there is no release for the Servlet 6.1 specification. Latest release of cdi spec it requires as...

Sure, however it is difficult. They seem to have removed all of the API that we were using instead of using infinispan annotations. Obviously, we can't annotate our generic Session...

Note to self: investigate this doco: https://infinispan.org/docs/stable/titles/query/query.html

I've asked 2 questions on stackoverflow: https://stackoverflow.com/questions/70887340/how-to-do-programmatic-indexing-with-infinispan-13 and https://stackoverflow.com/questions/76606148/how-to-do-programmatic-indexing-on-pojos-with-infinispan I also opened an issue on Infinispan issue tracker 18 months ago: https://issues.redhat.com/browse/ISPN-13486

You should be able to deploy multiple versions of jetty in the same OSGi container and have them resolve correctly by version. Whatever environment you're using seems to be resolving...