Jakarta-REST-4.0-Discussion is not publicly accessible

[anbusampath]

https://github.com/eclipse-ee4j/jaxrs-api/wiki/Jakarta-REST-4.0-Discussion - this page not accessible. Link is provided in roadmap page at the bottom - https://github.com/eclipse-ee4j/jersey/wiki/Road-Map

[jansupol]

It used to be there, but it is not any longer. Perhaps it is this project now https://github.com/jakartaee/rest/projects/2

[anbusampath]

Great, is there place to refer list of features tagged for 4.0 release?

[anbusampath]

I belive below links are slightly outdated.
https://projects.eclipse.org/projects/ee4j.rest/releases/4.0.0
https://jakarta.ee/specifications/restful-ws/4.0/

[jansupol]

This is what is going to be in 4.0: jakartaee/specifications#705

[martinofcourse]

I am sorry for piggybacking on this discussion, but couldn't find a better place to post.

If @Context is going to be deprecated, then how would one accomplish what @Context Application application does in an implementation-neutral way? For instance, when using SeBootstrap, the Application subclass is instantiated using new which thwarts CDI and @Inject won't work.

static CompletionStage<Instance> start(final Class<? extends Application> clazz, final Configuration configuration)

The comments to the above call explicitly state that Injection is not supported.

This also seem to effectively deprive us of the ability to perform eager initialization without observing events and writing an extension.

[martinofcourse]

Also, in jakarta.ws.rs.SeBootstrap I see

        default void stopOnShutdown(Consumer<StopResult> consumer) {
            Runtime.getRuntime().addShutdownHook(new Thread(() -> stop().thenAccept(consumer)));
        }

I could never get the consumer in the above to run before the JVM shuts down. I think if we want the CompletionStage<StopResult> stop(); and the consumer code to run before the JVM shuts down, we need something like this instead:

        default void stopOnShutdown(Consumer<StopResult> consumer) {
            Runtime.getRuntime().addShutdownHook(new Thread(() -> {
                stop().toCompletableFuture().thenAccept(consumer).join();
            }));
        }

Also, the CompletionStage twist on the stop() method seems superfluous when we are running off the new thread in the shutdown hook.