Artem Bilan

There is no "empty payload" support in Spring Messaging and exception states clearly about that: ``` org.springframework.messaging.converter.MessageConversionException: Cannot convert from actual payload type 'byte[]' to expected payload type 'java.lang.String' when...

Any news on this? Will it make in time for upcoming RC release cycle in a couple weeks? Or should I start looking into this as an interim home-made solution?...

See the fix I propose for Spring Integration for current situation: https://github.com/spring-projects/spring-integration/pull/3915. It looks like the `ExpressionBasedAuthorizationManager` has to be promoted to the top-level class as well.

Interesting... You know, I'm going to port Spring Integration Groovy DSL into core project soon enough: https://github.com/spring-projects/spring-integration-extensions/tree/main/spring-integration-groovy-dsl, but your catch still makes sense. I think we better look into this...

Any chances to see such a service in Groovy, which, as you said, comes with synthetic methods? Thanks

I have just confirmed that proposed `ClassUtils.isUserLevelMethod()` does the trick for such a Groovy class. There are some other issues in other places which use that `MessagingMethodInvokerHelper` as well, but...

@snicoll , I have figured out that I can get rid off `FactoryBean.OBJECT_TYPE_ATTRIBUTE` in favor of `setTargetType()`. Works well in plain JVM. It fails directly on AOT compilation phase just...

It looks like with generic argument we now expose on the `ProxyFactoryBean`, it works with AOT even without the mentioned `FactoryBean.OBJECT_TYPE_ATTRIBUTE` and without custom code. In the end it looks...

@garyrussell , I think this is good to go. Probably @snicoll is busy with other stuff. No worries: the fix is addressed exactly as it is expected in the issue...

Yeah... I will look into those, Stephane. It was really hard to find how to adapt to the latest Spring AOT changes. At the same time, I really might not...