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

Agile Board

Attach files

Attach Screenshot

Add vote

Voters

Watch issue

Watchers

Create sub-task

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Bug
Status: Open
Priority: Major
Resolution: Unresolved
Affects Version/s: None
Fix Version/s: None
Component/s: Conversation
Labels:
None

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.