Max
> That's expected, since they are transient, they aren't persisted. But shouldn't they be reevaluated after select?
> No, unless it's lazy. So what is the reason to have @transient vals at all? After select they are unusable. I think this is a bug. Even if @transient...
I've found more: all transient lazy val fields throw that exception but only if there is overridden transient lazy val toString. If it is tried to access transient lazy val...
Okay, I'm correct, transient val fields got reevaluated on select. Can't reproduce that first part. Now transient lazy vals. Transient lazy vals throw that ex if in the same class...
It also postpones graceful shutdown