春季整合支持寿命
我们处于基于JMS的新应用程序的设计阶段。我们正在考虑利用春季融合-JM。有一个关于计划支持的计划支持的问题，即将在将来为任何安全漏洞和将来可能出现的其他内容提供。
We are in the design phase of a new application JMS based application. We were thinking of making use of spring-integration-jms. Had one question about the planned support that will be provided for spring-integration-jms in future for any security vulnerabilities and other stuff that might appear in future.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
在stackoverflow上，这里的问题看起来并不有意义，但是作为项目领导，我可以回答您。
只要JMS规格在Java EE中不弃用和支持，我们将支持和维护
spring-integration-jms模块。实际上，在当前6.0版本中，我们甚至已经移动到jakarta.jmsnamespace。有关更多支持问题，请在此处联系： https://spring.io/support
Doesn't look like such a question makes sense over here on StackOverflow, but being a project lead I can answer you.
As long as JMS spec is not deprecated and supported in Java EE, we are going to support and maintain
spring-integration-jmsmodule. In fact in the current6.0version we even have moved tojakarta.jmsnamespace.For more support questions, please, reach out here: https://spring.io/support