Support @SchemaMapping + @BatchMapping on a class when looking for handlers along with @Controller

[geliotropvimd]

In this project, we have separated the processes of creating objects and mapping requests. We create objects through Kotlin DSL. @Controller breaks context startup.

Need like this

@SchemaMapping
class TestRes(
    private val testService: TestService,
    private val url: String,
) {
   @QueryMapping
    suspend fun test(): Test= Test(100, "100500")
}

But now we have to use workaround

@Controller
interface ControllerMarker

@SchemaMapping
class TestRes(
    private val testService: TestService,
    private val url: String,
): ControllerMarker {
   @QueryMapping
    suspend fun test(): Test= Test(100, "100500")
}

You need the ability to do the same as in the analogy with RSocket.

[rstoyanchev]

We haven't had a great experience with similar support in Spring MVC which treated a class-level @RequestMapping as a controller class. After running into multiple, independent issues with frameworks built on top, we're finally removing it in 6.0 spring-projects/spring-framework#22154.

In short, it wouldn't be an issue now, but as the ecosystem around it grows, it can become an issue, so I don't think this is something we'd want to introduce.

I'm not quite sure how @Controller breaks the startup? If it results in duplicate bean definitions, why is not an issue when it is defined on an interface instead? If this is the nature of the issue, do you have component scanning enabled, and if so can you try to configure it to be more precise?

[vladimirfx]

@Controller is composing 2 different concepts: bean registration AND request handling metadata.
In our projects, we use programmatic bean registration with Kotlin Bean DSL that conflicts with automatic bean registration provided by @Controller.
So we need annotation for pure request handling metadata without bean registration.

Analogically for @RequestMapping we fall in trouble after spring-projects/spring-framework#22154

[rstoyanchev]

@Controller is composing 2 different concepts: bean registration AND request handling metadata.

Yes but bean registration via component scanning is entirely optional. Especially for you situation, consider customizing it to select what packages to scan or turning it off in favor of explicit @Bean methods only.

[spring-projects-issues]

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

[spring-projects-issues]

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.