page-lifecycle

Today I'd like to know some features on the JSF Lifecycle. Let me start : 1 - Phase 2:Apply request Values - During this phase,each component in the view will search for its values in the request and set the new values to them Uhm, ok nice. So, the View will be built due to the previous Beans parameters. After, there is a partial View, generated with the request values. (Right? Later, in the 3° phase, they will be compared) . But, for example, if a values in the request list is absent during the creation of this last view? Values will be null? 2 - Phase 5: Invoke Application - Once all the

Could I get some confirmations from the community that I'm not going mad, and that the life cycle of a page during post back is in deed in a different order to when the page is initally requested. If this is the case pointers towards references/articles outlining the order would be greatly appreciated. (A postback equivalent of the page life cycle image would be great) The behaviour is slightly different but the order is the same. In this respect "Postback" is essentially a state flag on the request. http://msdn.microsoft.com/en-us/library/ms178472.aspx (nice image btw) edit: thinking about it

Everybody knows that you should close a connection immediately after you finish using it. Due to a flaw in my domain object model design, I've had to leave the connection open for the full page life cycle. Essentially, I have a Just In Time property which opens a connection on first call, and then on Page.Unload (..) it would check if a db connection was ever open, and then close it if it was. Since it only takes a second, I’ve had the opinion its not too much different than closing it immediately. Is this ok? Or should it still be closed immediately after every single use? Thanks in advance.

I have inherited a web framework whereby the previous developer has opened and closed his database connections in the init/unload methods of the page life cycle. Essentially constructor is like this (simplified to demonstrate the point); public class BasePage { protected DBConnection _conn; public BasePage() { Init += StartConnection; Unload += EndConnection; } private void StartConnection(object sender, EventArgs e) { _conn = new DBConnection(Application["connectionstring"].ToString()); } private void EndConnection(object sender, EventArgs e) { if (_conn == null) return; if (_conn.Connection

On Page_Init I create a table of dynamically created controls based on a couple of database tables. One of the controls is an ImageButton for moving an list item up the list. What this event handler does is to update the SortOrder column in the database for the affected items. Now the problem is that since the controls are created in the Page_Init event and the SortOrder is updated later on when the ImageButton command event is fired. What's the best procedure for updating the table with the correct SortOrder. If I recreate the table after the event has fired the ImageButton command event does