[ 
http://www.stripesframework.org/jira/browse/STS-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12440#comment-12440
 ] 

Ben Gunter commented on STS-688:
--------------------------------

Oscar, you're right, of course, about servlet mappings not behaving as 
prefixes. I think now I'm willing to concede that @UrlBinding probably 
shouldn't either. I'll look at changing this behavior for 1.6.

> Resolving UrlBindings incorrectly: an unbound URL does not yield a 404 error
> ----------------------------------------------------------------------------
>
>                 Key: STS-688
>                 URL: http://www.stripesframework.org/jira/browse/STS-688
>             Project: Stripes
>          Issue Type: Bug
>          Components: ActionBean Dispatching
>    Affects Versions: Release 1.5.1
>            Reporter: Oscar Westra van Holthe - Kind
>            Assignee: Ben Gunter
>            Priority: Minor
>             Fix For: Release 1.6
>
>         Attachments: STS-688.patch
>
>
> I have several ActionBean classes bound with these:
> @UrlBinding("/")
> @UrlBinding("/search/{text}")
> @UrlBinding("/profile")
> @UrlBinding("/admin")
> @UrlBinding("/admin/{username}")
> In addition to these, I have custom error pages defines for HTTP codes 403, 
> 404 and 500.
> When I navigate to /foobar I get the page for /, instead of the custom 404 
> error I expected.
> What goes wrong here is that the closest match, @UrlBinding("/"), has no 
> parameters. Therefore, it cannot match.
> The bug probably is in UrlBindingFactory.getBindingPrototype(String path); it 
> should check if a binding can match the URI. This probably only means an 
> added check to see if the binding has a parameter that can be filled in.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development

Reply via email to