Reputation: 4740
I'm out of ideas for my exception handling...
Using:
<myfaces.version>2.0.11</myfaces.version>
<richfaces.version>4.1.0.Final</richfaces.version>
<tomahawk.version>1.1.11</tomahawk.version>
<weld.version>1.1.4.Final</weld.version>
<codi.version>1.0.3</codi.version>
i plugged a simple exception handler that navigates to an error page.
Now an error raises in the render phase when accessing a bean value - it seems i can't change the navigation anymore (buffer already written?). The browser simply displays the partially rendered page. The state on the server seems to be corrupt from now as further requests contain the link to the old window scope - i always run in the same error.
How to handle such a case? Specification problem, MyFaces problem or developer problem?
Upvotes: 1
Views: 456
Reputation: 1109572
How to handle such a case? Specification problem, MyFaces problem or developer problem?
Developer problem. Don't do business logic inside a getter method. Do it in (post)constructor or (action)listener method instead.
Upvotes: 1