Closed GoogleCodeExporter closed 9 years ago
Original comment by balusc
on 12 Feb 2013 at 12:20
[deleted comment]
The problem is understood, but I'm inclined to say that this is "by design". A
single request parameter name can have multiple values. The <h:link
includeViewParams="true"> also works that way.
I could add a check which filters duplicate values on a single parameter, but
can't you for example just inject CompanyBean or even its compantId property in
AddressBean?
Original comment by balusc
on 12 Feb 2013 at 1:04
Well, your idea of injecting CompanyBean into AddressBean could work - but I
like my AddressBean with it's own params and -validation, usable after
initialization "by view" as the AddressBean can be used for other entities
(user, ...), too; Instead of injecting I choose to live with this urls.
Anyhow, I didn't know, that HTTP-GET params are allowed to have multiple values
- so, there is no problem from my point of view.
Original comment by markus.s...@wer-kennt-wen.de
on 12 Feb 2013 at 1:23
I decided to fix it anyway. The <f:viewParam> does at its own not support
multiple values, so having multiple <f:viewParam> tags on the same parameter
shouldn't be interpreted as a single parameter with multiple values.
http://code.google.com/p/omnifaces/source/detail?r=5329ccd5e2f7584c477c47d83345d
8c633c1151b
The attached snapshot contains the fix.
Original comment by balusc
on 12 Feb 2013 at 3:17
Attachments:
Original issue reported on code.google.com by
markussc...@gmail.com
on 12 Feb 2013 at 8:56