struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Don Brown (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (WW-2515) REST plugin does not throw a 404 if resource cannot be found
Date Fri, 02 May 2008 02:35:07 GMT

     [ https://issues.apache.org/struts/browse/WW-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Don Brown resolved WW-2515.
---------------------------

       Resolution: Not A Problem
    Fix Version/s:     (was: 2.1.2)
         Assignee: Don Brown

I think we determined there isn't a bug with how things work now.  Please open a new feature
ticket if you want the addition of exceptions that you can throw to get the 404 automatically.
 Patches welcome :)

> REST plugin does not throw a 404 if resource cannot be found
> ------------------------------------------------------------
>
>                 Key: WW-2515
>                 URL: https://issues.apache.org/struts/browse/WW-2515
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Plugin - REST
>    Affects Versions: 2.1.1
>         Environment: Struts 2.1.1-SNAPSHOT using Jetty 6.1.5
>            Reporter: Sarat Pediredla
>            Assignee: Don Brown
>         Attachments: WW-2515.patch
>
>
> When there is a GET request for a resource that does not exist, example GET /authors/25
where author with id 25 does not exist, the getModel() method of the action should return
null (and in most cases will return null as the object does not exist).
> However, the current ContentTypeInterceptor implementation is not entirely RESTful as
the right response should be HTTP Status Code 404 "Not Found".
> I have patched the ContentTypeInterceptor to return a 404 status if the requested resource
could not be found.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message