it means that in the explicit case if you do not wire a public render parameter then it is never possible to set it with a value which means that the portlet will not work as expected. "bdaw" wrote : &quot;julien(a)jboss.com&quot; wrote : one glitch I noticed is that in the explicit case, if a parameter is not explicit declared in a binding then it will simply never retain its state. | | | | It is visible in the explicit sample if you update PublicParametersPortletWindow1 juu1 parameter. The value is lost. | | | | I think it should rather remain private rather than being discarded, which would mean that in the explicit case this parameter is considered like a private parameters and is stored in the per window navigational state. Which would mean to add a Map<String, String[]> in the WindowNavigationalState to store such state. | | | | What do you think ? | | I remember we discussed it some time ago a bit. The thing is what behaviour would be expected. This would be the difference between FALLBACK and EXPLICIT strategy. In EXPLICIT param not wired is lost while in FALLBACK not. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166089#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...