Instead of doing straight JSR-168/286, step up to a framework that can handle ajax-based submission and refresh such as Vaadin or the like.
Basically what you're seeing is not a bug, it's part of the actual spec. It's why there's a separate action/render phase for portlets. For all of the portlets on a page, only one is called in the action phase (to handle the form submission), but all portlets on the page are called for their render phase (so the portal can aggregate the portlet content into a single page).
If you switch to an ajax-based framework, submits and refreshes would not go through the normal portal phase process, so you don't end up w/ full page refresh.
Por favor, identifíquese para poder marcar esto como inapropiado