-
1. Re: sending a class threw page parameters
pmuir Jun 26, 2007 2:54 PM (in response to adrien.loyat)You can't use the EntityConverter like that in pages.xml. Try something like
<param name="typecolId" value="#{colList.col.typecol.id}" />
Or write a custom converter that knows how to deal with a typecol object. -
2. Re: sending a class threw page parameters
adrien.loyat Jun 27, 2007 8:42 AM (in response to adrien.loyat)Thanks for your help. I've made it work with a custom converter.
I've tried many changes in the param without success. I'm a bit disappointed as, to my mind, this functionality should work easily in Seam without having to write a custom converter.
Best regards.
Adrien -
3. Re: sending a class threw page parameters
pmuir Jun 27, 2007 8:44 AM (in response to adrien.loyat)It does, just not the way you are going about it. There is lots in the manual about this, and the examples use this.
-
4. Re: sending a class threw page parameters
adrien.loyat Jun 27, 2007 9:22 AM (in response to adrien.loyat)I had a look at the examples but I didn't find anything looking exactly like my issue. My purpose was to, very quickly, add a new search parameter.
Maybe the way I do this is inappropriate but it seemed to me logical : I can search easily for colList.col.name (a string), so why is it difficult to search for colList.col.typecol (an entity) ? In fact, I was able to search for colList.col.typecol, but I was not able to click on the link so as to order the result because the typecol was then lost.
Sorry for my english, I try to make it comprehensible with difficulty.