[
http://www.stripesframework.org/jira/browse/STS-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Gunter closed STS-727.
--------------------------
> 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.1, Release 1.5.2
> Reporter: Kris Luhr
> Assignee: Ben Gunter
> Attachments: stripes-1.5.2-getBindingPrototype-bug.patch
>
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Stripes-development mailing list
Stripes-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-development
