Determining whether the current transaction has pending changes
This recipe shows you how to determine whether there are unsaved changes to the current transaction. This may come in handy when, for instance, you want to raise a warning pop-up message each time you attempt to leave the current page. This is demonstrated in the recipe Using an af:popup to handle pending changes in this chapter. Furthermore, by adding this functionality in a generic way to your application, making it part of the CommonActions framework for example, you can provide a standard application-wide approach for dealing with pending uncommitted transaction changes. The CommonActions framework was introduced in the Using a generic backing bean actions framework, Chapter 1,Pre-requisites to Success:ADF Project Setup and Foundations.
Getting ready
The functionality implemented in this recipe will be added to the ADFUtils helper class introduced in Using ADFUtils/JSFUtils, Chapter 1, Pre-requisites to Success: ADF Project...
