Convert a Kotlin Array to Java varargs: Passing Arrays to Java Methods from Kotlin

By the end of this page, you will understand how Kotlin handles Java varargs, why passing an array directly often fails, and how to use the spread operator (*) to expand a Kotlin array into individual arguments. You will also learn how to convert lists such as ArrayList<String> into arrays before passing them to Java varargs methods.

In Java, a method with varargs looks like this:

void antMatchers(String... patterns)

Java treats String... as a special syntax for “zero or more String values.” Internally, it is handled as a String[].

When Kotlin calls a Java varargs method, Kotlin does not automatically unpack an Array<String> into separate arguments. Instead, you usually need to explicitly tell Kotlin to spread the array into individual values.

That is what the * spread operator does.

web.ignoring().antMatchers(*angularRoutings)

This matters because Kotlin and Java interoperate closely, but their function call rules are not identical. If you regularly work with Java libraries from Kotlin, especially frameworks like Spring, Android APIs, or older utility libraries, you will often need to pass arrays or collections into Java varargs methods correctly.

For collections like ArrayList<String>, you cannot spread the list directly. A varargs parameter expects individual values, so you must first convert the list to an array:

val routes = arrayListOf("/language", )
web.ignoring().antMatchers(*routes.toTypedArray())

Think of a varargs method like a function that wants several separate items placed on a table:

• Java varargs: “Put each string on the table one by one.”
• Kotlin array: “Here is a box containing strings.”

If you hand over the box directly, the method may not treat it as separate items.

The spread operator * means:

“Open the box and place each item on the table individually.”

If you have a list instead of an array, you first need to pack it into the right kind of box (Array<String>) and then open it with *.

Core syntax

Passing individual values

web.ignoring().antMatchers("/language", "/home")

Passing a Kotlin array to Java varargs

val angularRoutings = arrayOf("/language", "/home")
web.ignoring().antMatchers(*angularRoutings)

Passing an ArrayList<String> or List<String>

val routes = arrayListOf("/language", "/home")
web.ignoring().antMatchers(*routes.toTypedArray())

Why * is needed

Without the spread operator:

val angularRoutings = arrayOf("/language", "/home")
web.ignoring().antMatchers(angularRoutings) // usually does not match the varargs call you expect

With the spread operator:

val angularRoutings = arrayOf(, )
web.ignoring().antMatchers(*angularRoutings)

Consider this example:

val routes = arrayOf("/language", "/home")
web.ignoring().antMatchers(*routes)

Step by step:

1. arrayOf("/language", "/home") creates a Kotlin Array<String>.
2. routes now holds two strings.
3. antMatchers(...) is a Java method that expects varargs, meaning multiple String arguments.
4. *routes tells Kotlin to spread the array.
5. Kotlin effectively turns the call into:

web.ignoring().antMatchers("/language", "/home")

1. The Java method receives the values as its varargs parameter.

Now compare with a list:

val routes = arrayListOf("/language", "/home")
web.ignoring().antMatchers(*routes.toTypedArray())

Step by step:

1. arrayListOf(...) creates an ArrayList<String>.

This pattern appears often when Kotlin code calls Java libraries.

Common scenarios

• Spring Security: passing URL patterns into methods like antMatchers(...)
• Logging frameworks: passing multiple formatting arguments
• Android APIs: calling Java methods that accept variable numbers of values
• Testing libraries: passing multiple expected values or parameters
• Utility libraries: methods like of(...), addAll(...), or matcher-style APIs

Example: route configuration

val publicRoutes = arrayOf("/login", "/register", "/about")
web.ignoring().antMatchers(*publicRoutes)

Example: dynamic values from configuration

val configuredRoutes = listOf("/health", "/metrics")
web.ignoring().antMatchers(*configuredRoutes.toTypedArray())

This is useful when the values are not hardcoded and come from files, databases, or application settings.

In real projects, developers often combine varargs calls with collection building, validation, and configuration.

Common patterns

1. Build a list, then convert once

If your values are dynamic, it is common to collect them in a list and convert at the call site.

val routes = mutableListOf("/home")
if (enableLanguagePage) {
    routes.add("/language")
}

web.ignoring().antMatchers(*routes.toTypedArray())

2. Guard against empty collections

val routes = getRoutesFromConfig()
if (routes.isNotEmpty()) {
    web.ignoring().antMatchers(*routes.toTypedArray())
}

3. Keep interop code local

A common style is to keep Java interop details near the boundary of the library call.

fun ignoreRoutes(web: WebSecurity, routes: List<String>) {
    web.ignoring().antMatchers(*routes.toTypedArray())
}

This keeps the rest of your Kotlin code clean and collection-friendly.

4. Prefer readable data preparation

val publicEndpoints = listOf(
    "/login",
    ,
    
)

web.ignoring().antMatchers(*publicEndpoints.toTypedArray())

1. Forgetting the spread operator

Broken:

val routes = arrayOf("/language", "/home")
web.ignoring().antMatchers(routes)

Fix:

web.ignoring().antMatchers(*routes)

2. Trying to spread a list directly

Broken:

val routes = listOf("/language", "/home")
web.ignoring().antMatchers(*routes)

A List<String> is not an Array<String>.

Fix:

web.ignoring().antMatchers(*routes.toTypedArray())

3. Confusing Java arrays and Kotlin collections

A Kotlin Array<String> and a List<String> are different types with different behaviors.

• Use Array<String> when you need array-based interop.
• Use List<String> for most regular Kotlin collection work.

4. Assuming varargs always accept collections

Array vs List when calling Java varargs

Direct arguments vs spread array

// Java method
// void antMatchers(String... patterns)

// Pass direct values
antMatchers("/language", "/home")

// Pass Kotlin array
val routes = arrayOf("/language", "/home")
antMatchers(*routes)

// Pass List or ArrayList
val routes = listOf("/language", "/home")
antMatchers(*routes.toTypedArray())

Rules

• Java String... becomes a varargs call from Kotlin.
• Use * to spread a Kotlin array into varargs.
• You cannot spread a List directly.
• Convert a list with toTypedArray() first.
• Array<String> and List<String> are not interchangeable.

Quick fixes

• Have Array<String>? ->

Why does antMatchers(array) fail in Kotlin?

Because Kotlin does not automatically expand the array into separate varargs arguments. Use *array.

How do I pass a Kotlin list to a Java varargs method?

Convert it first: *myList.toTypedArray().

What does the * operator mean in Kotlin?

It is the spread operator. It expands an array into individual arguments for a varargs parameter.

Can I use ArrayList<String> directly with varargs?

No. Convert it to an array first with toTypedArray().

Is Java String... the same as String[]?

Internally, yes. varargs is compiled as an array, but the call syntax is more flexible.

Should I use arrays or lists in Kotlin?

Use lists for most Kotlin code. Use arrays mainly when an API specifically requires them, such as Java varargs interop.

• Kotlin spread operator — directly related because * is the key to passing arrays into varargs.
• Kotlin arrays — important for understanding Array<String> and when arrays are needed.
• Kotlin lists and ArrayList — relevant because lists often need conversion before being passed to Java varargs.
• Java varargs — the underlying Java feature that Kotlin is calling.
• Kotlin Java interoperability — explains how Kotlin works with Java libraries and APIs.
• toTypedArray() — useful for converting collections into arrays for interop.
• Function parameters in Kotlin — helps clarify normal parameters versus varargs parameters.