Kotlin confuses which Spring method to call: ``` &...

# announcements

[Stephan Schroeder]

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?

[ribesg]

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

[Lawik]

What if you use named argument for requiredType?

[Lawik]

Nevermind, that's Java code and wouldn't work.

[Stephan Schroeder]

@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.

[Lawik]

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

[obobo]

since the 1st getBean has a parameterized type, would calling it as context.getBean<PipelineElementProcessor>(...) work?

[Stephan Schroeder]

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

[obobo]

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

[Stephan Schroeder]

it seems to be shadowed by the generic one.

[obobo]

try PipelineElementProcessor::class.java

[obobo]

instead of ::javaClass

[obobo]

I just tried it in a mock here, it worked, but with ::javaClass I had the same problem you did.

[obobo]

seems like javaClass shouldn't be invoked by reference, but instead on an instance of a class, since it uses the receiver to determine the type parameter.

[Stephan Schroeder]

yep, context.getBean(worker, PipelineElementProcessor::class.java) works 😃