Scala 2.11 @transient's are null

[MaXaMaR]

After loading of object from DB all @transient val fields are null.
lazy val fields throw
java.lang.ClassCastException: java.lang.Boolean cannot be cast to java.lang.Byte on access.

I think it has something to do with scala 2.11 because it seems that similar issues were fixed before.

[fwbrasil]

After loading of object from DB all @transient val fields are null.

That's expected, since they are transient, they aren't persisted.

lazy val fields throw
java.lang.ClassCastException: java.lang.Boolean cannot be cast to java.lang.Byte on access

That's interesting, could you share an isolated example of code that reproduces the issue?

[MaXaMaR]

That's expected, since they are transient, they aren't persisted.

But shouldn't they be reevaluated after select?

[fwbrasil]

But shouldn't they be reevaluated after select?

No, unless it's lazy.

[MaXaMaR]

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 var can be changed it is not normal that it is handling null.

[MaXaMaR]

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 field outside of transaction then this exception is thrown, not no transaction exception. It is also strange that it is required to have an active transaction to access lazy val field that already has all needed data.
activate-transient-lazy-val-fail.zip

[MaXaMaR]

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 some transient lazy val uses other transient lazy val. Seems like substitution doesn't work correctly.
activate-transient-lazy-val-fail.zip