Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Cannot Reproduce
-
Affects Version/s: Release 1.5.1, Release 1.5.2
-
Fix Version/s: None
-
Component/s: ActionBean Dispatching
-
Labels:None
Description
I would like to have a parameter first in my urls, representing different sections of a site; eg: @UrlBinding("/{section}/foo/bar/{$event}.html")
This UrlBinding results in a conflict between all ActionBeans using the {section} parameter. While debugging I find the UrlBindingFactory.getBindingPrototype(String uri) method ignoring the componentMatch when checking if we have a conflict, which seems to be a bug. At least in this case the result is not logical.
Additionally when I use the url "/section1/foo/bar.html", the section parameter is set to "section1/foo/bar".
This works and gives me the default handler if I dont have the section as a parameter. Perhaps these two issues are related?
Proposed patch for the conflict issue.
When removing the last slash I my tests pass the default handler issue, but the issue remains when I deploy the application. Is there another place with the same logic parsing urls somewhere?