Title: How to Override the Default Permission Security for an Existing Rave Model Object
Notice:    Licensed to the Apache Software Foundation (ASF) under one
           or more contributor license agreements.  See the NOTICE file
           distributed with this work for additional information
           regarding copyright ownership.  The ASF licenses this file
           to you under the Apache License, Version 2.0 (the
           "License"); you may not use this file except in compliance
           with the License.  You may obtain a copy of the License at
           .
             http://www.apache.org/licenses/LICENSE-2.0
           .
           Unless required by applicable law or agreed to in writing,
           software distributed under the License is distributed on an
           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
           KIND, either express or implied.  See the License for the
           specific language governing permissions and limitations
           under the License.


Click [here][1] first on how to extend Rave.

If you would like to override any of the various Default[ModelName]PermissionEvaluator classes supplied by Rave, it is easy to do.  For example, say you wanted to create your own ModelPermissionEvaluator for Page objects:

1) Create a class that extends AbstractModelPermissionEvaluator<Page>, such as CustomPagePermissionEvaluator, and make sure it is annotated as a Spring component:

    @Component
    public class CustomPagePermissionEvaluator extends AbstractModelPermissionEvaluator<Page> { ... }

2) Implement getType() to return Page.class

3) Override both hasPermission signature methods with your custom permission logic

4) Override the getLoadOrder function to return a larger number than 1.  This is important as it will make the RavePermissionEvaluator register your custom implementation for the Page object instead of the default ModelPermissionEvaluator for the Page object.

    @Override
    public int getLoadOrder() {        
        return super.getLoadOrder() + 1;
    }

5) Ensure your new class gets component scanned by Spring upon application startup.  Click [here][2] to read about how to override the application context. 


  [1]: rave-extensions.html
  [2]: custom-app-context.html