IssueTracker

As of now Google App Engine Standard Java 8 has reached end-of-support and will be deprecated soon (https://cloud.google.com/appengine/docs/standard/lifecycle/support-schedule).

However, the documentation only shows how to use Java 8 for GAE Standard with Endpoints Frameworks (https://cloud.google.com/endpoints/docs/frameworks/about-cloud-endpoints-frameworks).

There are some notes on this page (https://cloud.google.com/appengine/docs/standard/java-gen2/java-differences#framework_flexibility) for how to get off of legacy bundled services (and thus I assume, get off of Endpoints Frameworks) but there really isn't any comprehensive guide on how to migrate a GAE Standard Java Endpoints Frameworks project to a comparative solution. All there is, is a note saying "If your app does not use the legacy bundled services, you have to deploy a server yourself." - this isn't enough help because we don't know the best way to do that to keep our app functioning as expected. There are many options for web servers and it is unclear which is best to use with GAE to prevent interruption of service, bugs or security vulnerabilities.

What is needed is:
1. Documentation on how to migrate an existing GAE Standard Java Endpoints Frameworks project off of Endpoints Frameworks and create and deploy your own server. This includes migrating Endpoints Frameworks annotations and method decorations as well.

2. Documentation on how to migrate iOS, Android and Web client libraries that are generated by the Endpoints Frameworks. The ability to easily generate client libraries was a huge selling point of Cloud Endpoints ( for example: https://www.youtube.com/watch?v=A7yMmvrpMJc&ab_channel=GoogleforDevelopers). Another example: documentation such as this (https://cloud.google.com/endpoints/docs/frameworks/java/gen_clients) needs to be updated with migration solutions.

3. Documentation on how to create a new GAE Standard Java 11/17 Cloud Endpoints project without using Endpoints Frameworks is needed. This would be helpful for people who want to start over fresh with a GAE Standard Java Cloud Endpoints solution but do not want to deal with hassle of figuring out which Java web server to use. And also, have the ability to generate client side libraries to consume the api.