I have a lazy transient property in a `<http://java.io|java.io>.Serializable` class. However accessi...

# announcements

[rocketraman]

I have a lazy transient property in a <http://java.io|java.io>.Serializable class. However accessing foo from @delegate:Transient val foo: Foo by lazy { } causes a NPE on deserialization. How can I create a lazy property that the VM does not try to serialize, but at the same time does the right thing?

[Ryan]

Don’t use lazy or Don’t use seriazable?

[rocketraman]

No choice on the Serializable as its inherited from Apache Beam (and it uses it). Not using lazy is an option, but first I wanted to see if there was a way to make it work.

[gildor]

You probably should also annotate getter with Transient, @get:Transient

[rocketraman]

Tried that, results in a compile error

[gildor]

What kind error?

[rocketraman]

This annotation is not applicable to target 'member property with delegate' and use site target '@get'

[Ryan]

if i had to guess the private nullable variable isn’t getting those annots propegated to it

[Ryan]

i’ve stopped using lazy due to all the hiccups

[rocketraman]

I've worked around it by storing an `@Transient var`(non-lazy), and then re-setting it in readObject. There must be a more elegant approach though.