UrlBindingFactory interprets parameters first in url as conflict
----------------------------------------------------------------
Key: STS-727
URL: http://www.stripesframework.org/jira/browse/STS-727
Project: Stripes
Issue Type: Bug
Components: ActionBean Dispatching
Affects Versions: Release 1.5.2, Release 1.5.1
Reporter: Kris Luhr
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?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.stripesframework.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
