A bug that we've fixed in the ADF 10.1.3 release -- related to the inconsistent handling of EL expressions that reference data from binding containers other than the current page's like ${data.SomeOtherUIModel.SomeBinding} -- may impact your existing ADF web applications that may depend on this behavior when you upgrade them to 10.1.3.
I've posted a preview of the 10.1.3 release note item about this here, and have updated the ADF Binding Primer whitepaper to clarify the best practice of making sure each page refers only to bindings in its current binding container. The release note item suggests two alternative strategies to migrate occurrences of this in your existing applications if you have any.
10:00:00 AM 
|
