I have tested this problem again with the latest trinidad from the svn repository, and now the test results are a little bit different...

When I use CLIENT_STATE_METHOD 'all', it doesn't work anymore and I'm having this exception message (without stacktrace) when I click on a 'Show detail' link:

[ValueBindingImpl] Exception while determining read-only state of value-binding : #{adres.gemeente}

When I use CLIENT_STATE_METHOD 'token', everything works fine, but only when I don't use immediate="true" with the containing table! If I use immediate="true", any time I collapse the detail, I lose my changes when I submit. Is this the normal behaviour of the table component?

But if we don't use the immediate attribute, each time someone clicks on the 'hide' or 'show' link, all inputfields are validated, which is not the behaviour we want to have...

Regards,
Henk

Henk Vanhoe wrote:
Hi,

I am using an editable table inside a detailstamp facet. The data in the table comes from a request-scoped managed bean. As I want to avoid session scoped beans, I use the tomahawk savestate tag to save the state of my beans. Everything works fine, except that when I change something in this table and subsequently hide the table, my changes are not submitted (when I leave the detail expanded there is no problem). In my web.xml file I'm using the following options:

   <context-param>
       <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
       <param-value>client</param-value>
   </context-param>

   <context-param>
<param-name>org.apache.myfaces.trinidad.CLIENT_STATE_METHOD</param-name>
   <param-value>token</param-value>
 </context-param>
     <context-param>
       <param-name>
           org.apache.myfaces.trinidad.USE_APPLICATION_VIEW_CACHE
       </param-name>
       <param-value>true</param-value>
   </context-param>

   <context-param>
       <param-name>
           org.apache.myfaces.trinidad.CACHE_VIEW_ROOT
       </param-name>
       <param-value>true</param-value>
   </context-param>

I also noticed that when I change the org.apache.myfaces.trinidad.CLIENT_STATE_METHOD to 'all' instead of 'token', this problem goes away. Is this a bug?

Regards,
Henk



Reply via email to