+ Start a Discussion

Controller Extension Object Lifecycle

I notice that Visual Force controller extensions seem to act like session-level "backer beans", and are not constructed for each HTTP request like, for example, a JavaServer Faces request-level backer bean would be (as defined as such in faces-config.xml).


Is there any documentation that describes the precise lifecycle management of server-side objects that are instantiated and managed automatically by the Visual Force runtime, such as controllers and controller extensions?  I do not see this information in any of the PDF documents...






I am also interested in this documentation.  An installable package demonstration would be helpful.