@marc @amackenzie
Even with the workaround, I can’t get my application to work. I keep getting the following error:
required a bean of type ‘org.springframework.jms.config.JmsListenerEndpointRegistry’ that could not be found.
We use this Bean to help configure settings that support multitenancy. I see the class in spring-jms 5.3.24, included in the workaround pom, but the error comes nonetheless. I’m not sure if there is some issue caused by mismatched dependencies in the workaround.
It looks like there’s been talk of an upgrade to support Spring Boot 3 for a long time now. When is this supposed to be available? At my corporation we’ve been kicking critical XRAY vulnerabilities down the road that are all fixed in Spring Boot 3.x. Solace JMS seems to be the only thing blocking us from upgrading our entire microservice ecosystem the latest Spring Boot version.
Thanks,
Jeremy