Error because of wrong page definition/binding container

Question

Hello -
(Using JDev 10.1.3 JSF w/ADF BC)
I'm running into a weird "issue" involving setting up the binding container.
I have one page that has a table of data. I select a row and hit a button to navigate to a page with an edit form.
In the page definition (for the page with the edit form), I list a managed bean as the ControllerClass. (I use the bean as a PagePhaseListener.) I've also added bindings (#{bindings}) as a managed property for that bean.
In the managed bean I grab a hold of an attribute binding from the binding container in my beforePhase method (when the phase id is Lifecycle.PREPARE_RENDER_ID). However, I was always getting NULL for the attribute binding (which then caused a null pointer exception).
When I paused the execution in the debugger, it looks like the binding container was still set up for the previous page (the page with the table in it). Opening up the bindings variable, I found a member mBindingContainerDef which had members mObjName and mFullName which seemed to indicate that the binding container was the one for the previous page, NOT the page with my edit form. (mFullName had the full name and classpath for the first page's page definition.)
Why is this? I only indicate that the bean is a ControllerClass in the page definition for the 2nd page --> so shouldn't that be the binding container in effect when the PagePhaseListener methods are executed?
-- Scott

Answer 1

Scott,
I assume that your PhaseListener doesn'tdistinguish between the actual navigation and the JSF postback that is issued to the same page. In your case I assume that the PhaseListener is invoked on postback and thus ADF Faces points to the "old pagedef" file.
Frank