Sébastien Deleuze

I have dropped a comment in https://github.com/jakartaee/common-annotations-api/issues/124#issuecomment-1943490978 as it seems not realistic to me to just drop a bunch of annotations there, this topic is much more complex than that....

It looks like meta-annotation capabilities [have been removed from JSpecify 1.0](https://github.com/jspecify/jspecify/pull/339) so using them to meta annotate Spring annotations will not be possible. The other issue is that the "annote...

[JSpecify 1.0.0](https://jspecify.dev/blog/release-1.0.0) has been released. It does not provide meta annotation / implication capabilities yet so we will probably need to wait for JSpecify 1.1 to be able to leverage...

@rstoyanchev @snicoll Maybe the difference of behavior could be related to the fact that in `@ModelAttribute` + GET use case, `GenericTypeResolver#resolveType` is not invoked, while for `@RequestBody` + POST use...

I confirm the issue, likely caused by the `CoroutineContext` being overridden at [`CoExchangeFilterFunction` level](https://github.com/spring-projects/spring-framework/blob/main/spring-webflux/src/main/kotlin/org/springframework/web/reactive/function/client/CoExchangeFilterFunction.kt#L34), but I am not sure yet how we can pass properly the `CoroutineContext` until this point....

I have updated https://github.com/sdeleuze/spring-boot-leyden-demo to leverage the [new Leyden 1 step workflow](https://github.com/openjdk/leyden/tree/premain/test/hotspot/jtreg/premain/javac_new_workflow) that is much simpler to use than the previous 5 steps workflow. I think not all optimizations are...

See #32044 related documentation issue.

Spring team feedback sent to the `leyden-dev` mailing list about: - [Leyden-premain optimizations](https://mail.openjdk.org/pipermail/leyden-dev/2024-January/000497.html) - [Negative lookup cache for class loaders](https://mail.openjdk.org/pipermail/leyden-dev/2024-January/000498.html)

I think I like the direction taken by this proposal as Spring support for Coroutines is tightly linked to the Reactive support, and the scope of this issue is probably...

Regardless of the lack of `Charset.forName` implementation, I guess this will require platform (JavaScript now, potentially WASI later) integration right? I am wondering if we could take shortcut for such...