[
http://www.stripesframework.org/jira/browse/STS-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Gunter updated STS-665:
---------------------------
Fix Version/s: Release 1.5.2
> Resolution of URL binding conflicts depends on ActionBean class lookup order
> ----------------------------------------------------------------------------
>
> Key: STS-665
> URL: http://www.stripesframework.org/jira/browse/STS-665
> Project: Stripes
> Issue Type: Bug
> Components: ActionBean Dispatching
> Affects Versions: Release 1.5.1
> Reporter: Radu Butnaru
> Priority: Minor
> Fix For: Release 1.5.2
>
>
> I've noticed the following problem when resolving action beans for several
> (more than 2) conflicting clean URLs.
> Example:
> Three action beans bound to URLs:
> @UrlBinding("/customers")
> @UrlBinding("/customers/{customerName}")
> @UrlBinding("/customers/{customerName}/profile")
> Stripes randomly throws UrlBindingConflictException for the static URL
> '/customers' between servlet container restarts.
> Debugging showed that the problem seems to occur if the binding for the
> static URL is cached after the other two at startup during action bean
> resolution.
> When this was not the case, the behavior was as expected, i.e. the
> corresponding action beans were invoked for the three URLs.
--
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
------------------------------------------------------------------------------
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
