[
https://issues.apache.org/jira/browse/WW-4496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
adam brin updated WW-4496:
--------------------------
Description:
the struts static url mappings are great for simplifying URL paths and
including "data" in the URL structures. We're having collisions that are
causing problems though:
eg.
{quote}
class1:
@Namespace("/dataset/")
...
@Action("\X{id}")
...
class3:
@Namespace("/dataset")
...
@Action("columns/\X{id}")
{quote}
In this case, Class1's mapping seem to "own" everything under /dataset
regardless of what other classes like (class2) define. It'd be nice if struts
could, as it scans all of the namespaces and actions, evaluated left-to-right
non-programatically specified values ahead of those that are variables. E.g.
/dataset/columns/{id} would be evaluated prior to matching /dataset/{id}
was:
the struts static url mappings are great for simplifying URL paths and
including "data" in the URL structures. We're having collisions that are
causing problems though:
eg.
{quote}
class1:
@Namespace("/dataset/")
...
@Action("{id}")
...
class3:
@Namespace("/dataset")
...
@Action("columns/{id}")
{quote}
In this case, Class1's mapping seem to "own" everything under /dataset
regardless of what other classes like (class2) define. It'd be nice if struts
could, as it scans all of the namespaces and actions, evaluated left-to-right
non-programatically specified values ahead of those that are variables. E.g.
/dataset/columns/{id} would be evaluated prior to matching /dataset/{id}
> better reconciliation of static url mappings
> --------------------------------------------
>
> Key: WW-4496
> URL: https://issues.apache.org/jira/browse/WW-4496
> Project: Struts 2
> Issue Type: Improvement
> Affects Versions: 2.3.20
> Reporter: adam brin
>
> the struts static url mappings are great for simplifying URL paths and
> including "data" in the URL structures. We're having collisions that are
> causing problems though:
> eg.
> {quote}
> class1:
> @Namespace("/dataset/")
> ...
> @Action("\X{id}")
> ...
> class3:
> @Namespace("/dataset")
> ...
> @Action("columns/\X{id}")
> {quote}
> In this case, Class1's mapping seem to "own" everything under /dataset
> regardless of what other classes like (class2) define. It'd be nice if
> struts could, as it scans all of the namespaces and actions, evaluated
> left-to-right non-programatically specified values ahead of those that are
> variables. E.g. /dataset/columns/{id} would be evaluated prior to matching
> /dataset/{id}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
