Kotlin confuses which Spring method to call:

<T> T getBean(String name, Class<T> requiredType) throws BeansException;
	Object getBean(String name, Object... args) throws BeansException;

I want to call the former, but Kotlin calls the later and then flags my implementation as not guaranteeing the specified type

fun worker(worker: String): PipelineElementProcessor = try {
    context.getBean(worker, PipelineElementProcessor::javaClass)
}

Is there as solution apart from casting the result to PipelineElementProcessor?

Maybe

context.getBean<PipelineElementProcessor>(worker, PipelineElementProcessor::javaClass)

What if you use named argument for requiredType?

@ribesg that doesn’t even compile (“no type argument expected”). to be fair, that was my first instinct as well 😆. I’ve currently resigned to using

context.getBean(worker) as PipelineElementProcessor

but am still open to suggestions.

Is it possible to create extension functions for context which call the proper getBean functions?

since the 1st

getBean

has a parameterized type, would calling it as

context.getBean<PipelineElementProcessor>(...)

work?

nope -> compile msg: “no type argument expected”

weird. message makes me wonder if it is even seeing the method you want?

it seems to be shadowed by the generic one.

try

PipelineElementProcessor::class.java

yep,

context.getBean(worker, PipelineElementProcessor::class.java)

works 😃