servlet-api dependency major version change in micro release about hawtio HOT 6 CLOSED

Thanks for your reporting. I'm afraid we wouldn't likely address the issue, as Jetty 9 is EOL'ed in community. The only choice would be stay using <=2.17.4.

from hawtio.

I figured as much, thought I'd report it at least just in case. Seemed strange to make a large jump in dependencies in a micro version release. Thanks.

from hawtio.

@RangerRick you can install one bundle from Pax Web, which is roughly based on jakarta.servlet-api 4.0.4, but needs to work with Jetty 9.

If you install mvn:org.ops4j.pax.web/pax-web-compatibility-servlet31/8.0.24 having mvn:jakarta.servlet/jakarta.servlet-api/4.0.4 bundle installed, hawtio should work.

Also with Karaf it's a matter of installing pax-web-http-jetty|tomcat|undertow + pax-web-war features and then hawtio-osgi wab.

from hawtio.

Ooh, I'll give that a shot. We have a weird embedded monster in our code and are only using half of pax-web's stuff for terrible historic reasons, but that might just do it. Thanks!

from hawtio.

I know a but about weird embedded monsters ;)

from hawtio.

LOL, well, we had a bunch of existing web/servlet infrastructure, so we ended up embedding Karaf in our core Spring (non-boot) app, after Jetty has initialized, so we can share classpath with it and slowly migrate things to OSGi. It solved the problem at the time better than anything else, but hoo boy it is a mess and it's been slow moving things into the container. We have our own hacked up whiteboard bridge to make it work.

from hawtio.