This change has proven to be the right thing.

Checked in SeamUtilities.java in version 13640, removing the call to beforeRedirect.

Oddly, the error doesn't show up in the example applications, and the workaround affects nothing. The workaround is necessary for my more complete test page however, and the behaviour now conforms perfectly to the non-icefaces application testcase.

The SeamUtilities class was changed on December 4, 2006 to call beforeRedirect on the Seam Manager class. This was necessary to duplicate what the SeamRedirectionFilter was doing for Seam only applications.

The api was changed in Seam 1.2.1, and JIRA-1412 comments on that fix

In doing some testing for this case, it looks like calling this method is no longer necessary at all. I'm looking into what changed. The beforeRedirect method on the Manager class has a bistate side effect which breaks the application behaviour if called an odd number of times. It doesn't affect the example applications, which use Seam Link tags to navigate through the application, but it does affect the test project, which uses pages.xml to navigate through the application, and to manage the conversations.

In my tests, any page navigation done with pages.xml appears to start a conversation that cannot be ended, without the workaround.

Commenting out the call to beforeRedirect from the SeamUtilities class fixes the problem. I'm testing more applications to try to be sure.