Hi Craig, sorry it wasnt my intention to attack shale ;-)
As Simon points out, managed bean property initialization occurs *only* if the managed bean facility actually created the bean. This is exactly equivalent to the way that <jsp:setProperty> elements inside a <jsp:useBean> element are *only* processed if the bean was actually created. It has nothing to do with Shale -- this is fundamental to the way that the JSF specification defines the functionality of the managed bean facility.
Ok, now I got it!
So my next guess is: I use saveState and then the bean isnt generated through the managed bean facility and thus no managed property configuration will be processed.
I'll look in this direction. --- Mario
