This works: ```@SolrDocument(solrCoreName ="indexe...

# getting-started

[bjonnh]

This works:

@SolrDocument(solrCoreName ="indexedcitation")
class IndexedCitation {
    @Id
    @Indexed(name = "id", type = "string")
    private var id: String? = null

    @Indexed(name = "title", type = "string")
    private var title: String? = null


    fun getId(): String? {
        return id
    }

    fun setId(id: String?) {
        this.id = id
    }

    fun getTitle(): String? {
        return title
    }

    fun setTitle(title: String?) {
        this.title = title
    }
}

but not:

@SolrDocument(solrCoreName ="indexedcitation")
data class IndexedCitation(
    @Id
    @Indexed(name = "id", type = "string")
    private var id: String? = null,

    @Indexed(name = "title", type = "string")
    private var title: String? = null

)

[Pavlo Liapota]

You can specify for which element annotation should be used:
https://kotlinlang.org/docs/reference/annotations.html#annotation-use-site-targets

[bjonnh]

so correct me if I'm wrong but in that case it would be @field:String ?

[Pavlo Liapota]

@field:Id
I don’t know which target you need (field, set or get), you can try several.

[bjonnh]

I can't set these on the @Indexed parameters

[bjonnh]

and trying all combinations on @Id do not change anything (the only one that work on @Indexed is field.

[bjonnh]

https://gist.github.com/bjonnh/5493eb89fbc0207679d75cab8b3938b1

[bjonnh]

bytecode of the dataclass

[bjonnh]

https://gist.github.com/bjonnh/bc91bedd8b23dccbfd947d9a8d707b42

[bjonnh]

bytecode of the public class

[bjonnh]

(no idea if it is useful or not)

[bjonnh]

ok it seems that the problem arises when I have a constructor

[Robert Jaros]

Do you use allopen plugin? the classes are final in the bytecode you posted and spring doesn't like final classes - it can give weird errors.

[bjonnh]

what is that plugin?

[bjonnh]

(reading https://www.baeldung.com/kotlin-allopen-spring)

[bjonnh]

Is there any expected negative side effect of using that plugin?

[Robert Jaros]

not really

[Robert Jaros]

all your classes will be open by default just like in Java

[Robert Jaros]

there is also kotlin-spring plugin, which works the same way but only for classes annotated with Spring annotations

[Robert Jaros]

https://kotlinlang.org/docs/reference/compiler-plugins.html#spring-support

[Robert Jaros]

definitely worth applying before testing spring with kotlin

[bjonnh]

first time I get stung by that but yep I'll clearly try that

[bjonnh]

But I cannot make data classes open

[bjonnh]

seems to work anyway. Thanks