+++ /dev/null
-/*******************************************************************************\r
- * ============LICENSE_START====================================================\r
- * * org.onap.aaf\r
- * * ===========================================================================\r
- * * Copyright © 2017 AT&T Intellectual Property. All rights reserved.\r
- * * ===========================================================================\r
- * * Licensed under the Apache License, Version 2.0 (the "License");\r
- * * you may not use this file except in compliance with the License.\r
- * * You may obtain a copy of the License at\r
- * * \r
- * * http://www.apache.org/licenses/LICENSE-2.0\r
- * * \r
- * * Unless required by applicable law or agreed to in writing, software\r
- * * distributed under the License is distributed on an "AS IS" BASIS,\r
- * * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\r
- * * See the License for the specific language governing permissions and\r
- * * limitations under the License.\r
- * * ============LICENSE_END====================================================\r
- * *\r
- * * ECOMP is a trademark and service mark of AT&T Intellectual Property.\r
- * *\r
- ******************************************************************************/\r
-/**\r
- * RolesAllowed \r
- * \r
- * \r
- * Similar to Java EE's Spec from Annotations 1.1, 2.8\r
- * \r
- * That Spec, however, was geared towards being able to route calls to Methods on Objects, and thus needed a more refined\r
- * sense of permissions hierarchy. The same mechanism, however, can easily be achieved on single Servlet/Handlers in\r
- * POJOs like Jetty by simply adding the Roles Allowed in a similar Annotation\r
- * \r
- */\r
-package org.onap.aaf.cadi.filter;\r
-import static java.lang.annotation.ElementType.TYPE;\r
-import static java.lang.annotation.RetentionPolicy.RUNTIME;\r
-\r
-import java.lang.annotation.Retention;\r
-import java.lang.annotation.Target;\r
-\r
-/**\r
- * JASPI Style Annotation of RolesAllowed when the coding style is desired but actually including all \r
- * JEE jars is not. If using actual JASPI, use official @interface classes, not this one...\r
- * \r
- */\r
-@Target({TYPE})\r
-@Retention(RUNTIME)\r
-public @interface RolesAllowed {\r
- /**\r
- * Security role of the implementation, which doesn't have to be an EJB or CORBA like object. Can be just a\r
- * Handler\r
- * @return\r
- */\r
- String[] value();\r
-}\r