ADF viewScope is creating new instance without navigating away from view

Question

Hello,
I'm using JDeveloper version 11.1.1.6.0.
In a Portal application, I'm using view scoped Managed Beans. When I navigate to a page, as expected one instance of the Bean is created. I have dependent selectOneChoice objects inside this page, therefore a partial page refresh is generated when the user chooses a value, a value change listener is called, I read bean variables and do my thing. But here's the catch, a new instance of the Managed Bean is created before the value change listener is called. I have no idea why. According to documentation the viewScope bean should persist until the viewId changes. The end result is I'm screwed trying to read variables that should persist from page load inside this value change listener.
But wait, that's not all. The issue here is the very first partial page refresh (or whatever it should be called). Only the first partial page refresh will cause the creation of a new managed bean instance. Any subsequent ones will not.
So it goes like this:
Page load -> @PostConstruct runs once -> Partial page refresh -> @PostConstruct runs again -> Partial page refresh -> @PostConstruct doesn't run -> Partial page refresh -> @PostConstruct doesn't run...
I'm really at a loss of options here, the @PostConstruct running twice inside the very same view in a viewScope Bean is news to me. But then again, I'm new to ADF so what do I know. I noticed this happens with every viewScope bean in my application, not just this particular one. It just so happens that only in this case this became a problem.
I'm in an all out war against this thing for more than a day now. The internet is my last resort before I make some dumb workaround that will consume me in my sleep. Any help is greatly appreciated.
Edited by: 934172 on Sep 6, 2012 12:35 PM
Edited by: 934172 on Sep 6, 2012 12:36 PM

Answer 1

I'm determined to fix this thing no matter what the hell it takes.
I found out exactly what is happening, even though I'm not sure why it happens. But the important question here is how to fix it.
Here is the first request, the one that happens when I navigate to the page:
http://localhost:7101/teste-Portal-context-root/faces/pages_test?_adf.ctrl-state=18hjxv8lyw_4Here are all the subsequent ones, the ones that happen when I select a choice:
http://localhost:7101/teste-Portal-context-root/faces/oracle/webcenter/portalapp/pages/test.jspx?_adf.ctrl-state=18hjxv8lyw_4It's no wonder the server is confused and creates a new bean instance. Now what the hell? Why are they different? But more importantly, can I fix the first one? Can I force the bean created by the first one to answer for the second one?
I still don't know. But hopefully I'll find out.