You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Ivan (JIRA)" <ji...@apache.org> on 2010/09/25 03:43:32 UTC

[jira] Resolved: (GERONIMO-5577) Support ServeltSecurity annotation when the servlets are added by ServletContext.addServlet methods

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

Ivan resolved GERONIMO-5577.
----------------------------

    Fix Version/s: 3.0
       Resolution: Fixed

This patch is included in the commit at rev. 1000329, thanks, Han Hong Fang !

> Support ServeltSecurity annotation when the servlets are added by ServletContext.addServlet methods
> ---------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-5577
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5577
>             Project: Geronimo
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: web
>    Affects Versions: 3.0
>            Reporter: Han Hong Fang
>            Assignee: Ivan
>             Fix For: 3.0
>
>         Attachments: GERONIMO-5577.patch
>
>
> Servlet 3.0 spec has following statements in chapter 13.4.1.
> The @ServletSecurity annotation provides an alternative mechanism for
> defining access control constraints equivalent to those that could otherwise have
> been expressed declaratively via security-constraint elements in the portable
> deployment descriptor or programmatically via the setServletSecurity method
> of the ServletRegistration interface. Servlet containers MUST support the use
> of the @ServletSecurity annotation on classes (and subclasses thereof) that
> implement the javax.servlet.Servlet interface.

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