Currently we don't reinject fields after activation, though I kind of think we should. I'll try to find out why that note is in the spec, as to me it seems clearcut that we should perform injection after activation for transient injectable fields.
Well, the problem is that it can't be made to work for constructor injection.
I turns out beeing serializable is a strict requirement for session scoped webBeans but wasn't for session scouped JSF beans.
Serializability is a strict requirement for anything you put in the HttpSession. Unfortunately, this requirement is not enforced upfront by some web containers and is apparently not validated by your JSF implementation.
It's much better that web beans does actually validate these things and auto-detects your programming errors, right?
I agree failing at deployment time is much better thant failing at a later time.
About reinjecting transitive fields: I thinks this is really needed. I understand it can't be done for Constructor parameters but having it work for injected fields and not for Constructor is still better then having it for non of both.
By the way I've to say I'm very happy with the fast, friendly and helpfull responses in this forum. Despite the fact that its not final playing with jsr299 / Webbeans is really fun.