[ORCHESTRA-38] richfaces command components don't work with o:separateConversationContext

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Conversation
• Assignee: Unassigned
• Reporter: Simon Kitching
• Created: 22/Feb/09 13:13
• Updated: 22/Feb/09 13:13

Description

As reported by Bernd Winterstein, a richfaces commandButton opens the new page in the same conversation context even when o:separateConversationContext is used.

I suspect that the problem is that in the problem case, the commandButton is in an ajax panel that has been already refreshed at least once. And that when a richfaces ajax panel refreshes, the o:separateConversationContext tag outside of the panel is not executed and therefore has not set the magic flag that tells EncodeURL to skip adding the conversationContext=?? parameter.

If this is the case, then perhaps the solution involves the EncodeURL method actively looking for an ancestor component of type o:separateConversationContext rather than just checking the global flag. Or some kind of hook for the start of the richfaces rendering that looks for any ancestor o:separateConversationContext component.