Rogerio Pereira schrieb:
saveState never save objects in session, this component is used to avoid session overload, saveState serializes all objects somewhere in you filesystem.
This is not entirely true savestate uses the standard jsf save and restory cycle to store the data. It simply serializes the referenced bean and deserialises it. It now depends on the save and restore settings of the jsf implementation where the data is stored. If you have client side state saving it will store the data into the browser, if you have server side it depends on where the server side state saving is stored to. Depending on the settings it stores it into the session or somewhere else.
Werner
