If you are doing this work, use Jetty 9.4.20.v20190813, not 9.4.18. (and
stay current)


> 1) we are using  org.eclipse.jetty.server.AsyncContinuation.


Starting in Servlet 3.0 (Jetty 8.1.x) you should have transitioned to using
the standard async techniques.

Look at javax.servlet.AsyncContext and switch to using it.
The methods names should seem familiar.

See https://docs.oracle.com/javaee/7/api/javax/servlet/AsyncContext.html

While the continuation classes are still present in Jetty 9.4.x they are
deprecated and fully removed in Jetty 10.0.x

https://github.com/eclipse/jetty.project/blob/jetty-9.4.20.v20190813/jetty-continuation/src/main/java/org/eclipse/jetty/continuation/Continuation.java#L140-L143


2) We are using AbstractHttpConnection.   specifically
AbstractHttpConnection.getCurrentConnection()
> method.
> 4) we are using connector.getConnection() method.


Accessing the Connection is a strong anti-pattern.
Why are you doing this?


3) We are using org.eclipse.jetty.security.MappedLoginService which is not
> present in Jetty 9.4.18.


The entire security layer was refactored in Jetty 9.x
What specific feature of MappedLoginService were you using?
Based on your answer we can point you to the correct code.

Joakim Erdfelt / [email protected]


On Thu, Sep 5, 2019 at 11:30 AM anand patel <[email protected]>
wrote:

> Hi Team,
>
> Currently we are using Jetty 8.1.12 with JDK8. We are migrating to JDK11.
> As per this documentation
> <https://www.eclipse.org/lists/jetty-announce/msg00124.html>, Jetty
> 9.4.12 onward it is fully compatible with JDK11. (Also as per this
> <https://www.eclipse.org/lists/jetty-announce/msg00125.html>, they
> encourage old jetty users to upgrade to latest version as soon as
> possible). Because of dependency on some classes which are absent in Jetty
> 9.4.x, we can’t move from 8.1.12 straight forwardly.
>
> I wanted to know if anyone has faced any issue with Jetty 8.1.12 and JDK11
> or not. And if yes, do you have list of known compatibility issues and any
> guidance for the same?
>
> Also, while migrating to Jetty 9.4.18. I am facing following issues:
>
> 1) we are using  org.eclipse.jetty.server.AsyncContinuation. Which is not
> present in Jetty 9.4.18
> 2) We are using AbstractHttpConnection.   specifically 
> AbstractHttpConnection.getCurrentConnection()
> method. Which is not present in Jetty 9.4.18.
> 3) We are using org.eclipse.jetty.security.MappedLoginService which is not
> present in Jetty 9.4.18.
> 4) we are using connector.getConnection() method. which is not present in
> Connector class in Jetty 9.4.18.
>
> Thanks,
> Anand.
> _______________________________________________
> jetty-users mailing list
> [email protected]
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/jetty-users
_______________________________________________
jetty-users mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/jetty-users

Reply via email to