java.lang.IllegalArgumentException: page parameter may not be multi-valued

esmond.pitt Nov 13, 2008 4:09 AM

I don't think the answer given there is correct. We have several pages with params defined and links to those pages with f:params defined and it all works OK unless a parameter value contains a /, which appears as %2f in the actual URL of course. Somehow that causes not just that parameter but all parameters, or possibly the first parameter, to be treated as multi-valued.

I am wondering whether the true explanation isn't this thread about incorrect ordering of conversion and validation.

In this particular case I'm wondering whether the / and %2f are being seen as different because of the incorrect ordering referred to there.

TIA

EJP

1. Re: java.lang.IllegalArgumentException: page parameter may not be multi-valued

esmond.pitt Jan 15, 2009 2:32 AM (in response to esmond.pitt)

In fact the answer is clearly incorrect, as the technique is used in the Seam examples for pagination: you specify an f:param page in the page.xml file, and another f:param page value under an s:link.

Clearly a Seam bug. It appears to me that page parameters are being URL-decoded twice somehow. Will follow up.
Actions