Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: Release 1.5
-
Fix Version/s: Release 1.5.1, Release 1.6
-
Component/s: ActionBean Dispatching
-
Labels:None
Description
This is best explained by example.
Clean URL binding: /search/show/{p=1}.action
In this case, p is a page number and I want the default page number to be 1. Generated links with no p parameter will generate /search/show/1.action. The following URLs yield the indicated value for p in the ActionBean:
/search/show/1.action ... p=1 because it is specified in the URI
/search/show.action ... p=1 because that is the default value and it is not otherwise specified
/search/show.action?p=2 ... p=1 because that is the default value
In the last case, since p is specified in the query string, p should equal 2. Values in the query string should override clean URL default values.
One more related problem is that parameters submitted as part of a multipart request are not accounted for either. Parameters in both the query string and in the multipart request should override the default value for URI parameters.