In particular, the supplied {@link Context} instance contains the {@link Session} that is calling this provider, allowing theprovider implementation to access authorization-specific content within the repository to determine permissions for other repository content.
In these cases, calls to the session to access nodes will result in their own calls to {@link #hasPermission(Context,Path,String)}. Therefore, such implementations need to handle these special authorization-specific content permissions in an explicit fashion. It is also adviced that such providers cache as much of the authorization-specifc content as possible, as the {@link #hasPermission(Context,Path,String)} method is called frequently.
|
|