On Mon, 7 Nov 2005, Tim Davies wrote:
I had a similar problem, or at least sympton when I first started using MyFaces. For me it was occurring as a result of redirects however. The solution I found to the problem was to call the method "FacesContext.getCurrentInstance().responseComplete()" after every time that I sent a redirect. This solved the problem instantly.
When I said that my web application has a series of pages, I wasn't perhaps being as clear as I should have been - there's only one jsp file, and forward and back commandButtons are used to update a page property in the backing bean.
Anyway, the test case in the JIRA entry just consists of one page, its commandButton is not bound to any method, and the exception is thrown when MyFaces it calls ServletExternalContextImpl.dispatch to forward to the JSP page to render the response.
Jeremy
