[gavin.king]

I already told you this several hours ago:

I actually *did* change something in CVS very recently, by putting the conversation id in the PAGE context, instead of directly into the ViewRoot attribute map.

However, this should be perfectly OK to do.

But we are no closer to discovering why this does not work in your environment when it works perfectly well in the demo apps....

[crnip]

I do remember That you told me this, but then you implied that this should not be causing any problems. Now I do now that exactly this is cousing problem but it is bound to my application settup. Because of this I will investigate this a little further when i will have time. For now i spent to much on this issue. When i will now something more i will notify you. I think this is bound to ADF Faces components.

BTW: BackButton on page flows produces an error. When you check if page is backable then getPage() method returns null and NullPointerException is issued. Maybe this was allready corrected. This is just for reminder.

[gavin.king]

"crnip" wrote:
BTW: BackButton on page flows produces an error. When you check if page is backable then getPage() method returns null and NullPointerException is issued. Maybe this was allready corrected. This is just for reminder.

Again, I have never seen this. This is working fine in the dvd example app.

If you can produce some ultra-simplified toy example app that reproduces these problems I will take a look. But otherwise there is nothing much that I can do from my end...

[jcruise]

I am not sure if this is related, but I lost conversation propogation in an ADF faces app after I switched to using a post beta 2 daily. It seems like the state manager in seam wasn't being loaded and so the long lived conversations were not being persisted at all.

To fix this problem I have had to add a config entry in faces config to load the Seam state manager alongside the adf faces state manager.

My application entry in faces-config now looks something like:

 <application>
 <view-handler>oracle.adfinternal.view.faces.application.ViewHandlerImpl</view-handler>
 <state-manager>oracle.adfinternal.view.faces.application.StateManagerImpl</state-manager>
 <state-manager>org.jboss.seam.jsf.SeamStateManager</state-manager>
 <navigation-handler>oracle.adfinternal.view.faces.application.NavigationHandlerImpl</navigation-handler>
 <variable-resolver>oracle.adfinternal.view.faces.el.AdfFacesVariableResolver</variable-resolver>
 <default-render-kit-id>oracle.adf.core</default-render-kit-id>
 </application>

I know that adf faces and I presume Seam specify some of these components inside their private faces-configs, but it takes the above application definition to get them working together for me.

Better suggestions are much appreciated.

Cheers
J

[gavin.king]

If ADF completely replaces the JSF state manager (instead of wrapping and delegating), then that would certainly break Seam.

Seam depends upon its state manager being called to save the conversation id.

So, it seems like you have found the cause and the correct fix.