ADF Region to Parent Communication

Question

ADF 11.1.1.6, jdk 1.6.37, Windows 7 x64
Use Case:
I have a Parent with a region (train).
I have a button in the region(jsff) on the second page of the train (add record) and a button (Save) located in the parent page (jspx).
When I enter the form the save should be disabled until the add record is pressed.
I have tried a contextual event - without success. The event triggers OK - but there is no "real" communication to the button to tell it to look at the value.
I use a "buttonPressed" variable in the AM to store the state. (getters and setters do the major work of keeping the AM in sync)
Basically I want the event to trigger the refresh of the button in the parent page - so it will look at the value in the AM.
I want to keep the button disabled until a record is added in the second page of the train.
Anyone solved this type of issue before? (it is similar to the issues around dirty records in a region not propagating to the parent)
It would be simple if the region could do a programmed refresh on the parent button. (Is there a way to get the parent context? and would the backing bean still be active?)

Answer 1

Hi,
you need a mix of two for this usecase
1. RegionNavigationListener to tell when you enter the form. Fromthe region navigation listener you can tell the viewId the page fragment in the region has. So this will then allow you to disabled the button in the parent view
2. You need to pass a managed bean in view scope from the parent page as an input parameter to the region (task flow). This method will need to have a method that understands how to access the command button in the parent page and enabled it (+ refresh with PPR). Because you "injct" the managed bean from the parent view into the task flow, its context remains in the parent view. So you can look up the command button on the Faces Context (you cannot use JSF component binding in a bean that is in view scope). Alternatively you create a second bean in the parent view, which is in backingBeanScope and that holds the JSF component binding to the button. You then access the bean in backing bean scope (using EL in Java) from the managed bean in view scope to get a handle to the component binding)
Frank