码头升级8至9 [英] Jetty upgrade 8 to 9
问题描述
当我尝试从Jetty 8.1.12迁移到Jetty 9.4.18时，由于以下问题，我遇到了错误.
When I am trying to migrate to Jetty 9.4.18 from Jetty 8.1.12, I am getting errors because of following issues.
- 我们正在使用org.eclipse.jetty.server.AsyncContinuation.在Jetty 9.4.18中不存在
- 我们正在使用AbstractHttpConnection.特别是AbstractHttpConnection.getCurrentConnection()方法. Jetty 9.4.18中不存在.
- 我们正在使用Jet.9.4.18中没有的org.eclipse.jetty.security.MappedLoginService.
- 我们正在使用connector.getConnection()方法.在Jetty 9.4.18的Connector类中不存在.
在Jetty升级页面上没有找到关于这些问题的任何文档.
I did not find any documentation in Jetty upgrade page for these issues.
推荐答案
欢迎使用Stackoverflow！
Welcome to Stackoverflow!
在一个问题上问多个不相关的问题不是一个好主意.
It is not a great idea to ask multiple unrelated questions on a single question.
1)我们正在使用org.eclipse.jetty.server.AsyncContinuation.在Jetty 9.4.18中不存在
1) we are using org.eclipse.jetty.server.AsyncContinuation. Which is not present in Jetty 9.4.18
AsyncContinuation是Jetty 7和更老的概念.
AsyncContinuation is an Jetty 7 and older concept.
它被保存在Jetty 8中，作为对Servlet 3.0中引入的Servlet规范特定于异步的行为的转换(在Jetty 8.x中受支持).
It was kept in Jetty 8 as a transition to the Servlet spec specific behaviors regarding async that were introduced in Servlet 3.0 (supported in Jetty 8.x).
切换为改用 javax.servlet.AsyncContext . (您会发现许多方法名称都是相似的，因此过渡不应该那么麻烦).
Switch to using javax.servlet.AsyncContext instead. (You'll find many of the methods names to be similar, so the transition shouldn't be that problematic).
2)我们正在使用AbstractHttpConnection.特别是AbstractHttpConnection.getCurrentConnection()方法.在Jetty 9.4.18中不存在
2) We are using AbstractHttpConnection. specifically AbstractHttpConnection.getCurrentConnection() method. Which is not present in Jetty 9.4.18
如果您要访问原始Connection，您将面临无尽的问题. Connection对象不再代表物理连接，它通常代表虚拟连接，并且可以在物理连接的生命周期内进行更改或替换.您未能解释为什么需要这样做，以及在何种情况和环境下需要这样做.
If you are accessing the raw Connection you will have an endless stream of issues ahead of you. The Connection object no longer represents the physical connection, it often represents a virtual connection and can mutate or be swapped out through the lifespan of a physical connection. You have failed to explain why you need this, and under what kind of situations and environments you need this.
在stackoverflow上创建一个新问题，解释为什么需要这个，以及要解决的目标. (不是您之前使用的技术，目标，最终结果)
Create a new question on stackoverflow explaining why you need this, and what goal you are attempting to solve. (not the techniques you were using before, the goal, the end result)
3)我们使用的是Jetty 9.4.18中不存在的org.eclipse.jetty.security.MappedLoginService
3) We are using org.eclipse.jetty.security.MappedLoginService which is not present in Jetty 9.4.18
整个安全层都经过了重构，没有您正在尝试的操作的详细信息，因此不可能将您指向正确的外观.
The entire Security layer was refactored, without details on what you are attempting, it would be impossible to point you to the correct place to look.
也为此问题在stackoverflow上创建(另一个)问题.解释您要解决的问题，显示一些代码.在详细说明问题时，首先要关注目标，然后才是尝试的技术.
Create (another) question on stackoverflow for this one too. Explain what you are attempting to solve, show some code. When detailing your question focus on the goal first, then the techniques you have attempted.
4)我们正在使用connector.getConnection()方法.在Jetty 9.4.18的Connector类中不存在.
4) we are using connector.getConnection() method. which is not present in Connector class in Jetty 9.4.18.
这似乎与问题3重叠. 但是在这种问题上没有任何处理.
This seems to overlap with question 3, perhaps. But there's nothing to work with on this kind of question.
这篇关于码头升级8至9的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
