[ 
https://issues.apache.org/jira/browse/JENA-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631660#comment-14631660
 ] 

Andy Seaborne commented on JENA-990:
------------------------------------

> AddDeniedException and DeleteDeniedException will extend 
> AccessDeniedException.

Won't it be better if AddDeniedException and DeleteDeniedException, as in 
jena-core default implementation of unimplemented operations extend 
OperationDeniedException?

AccessDeniedException extends OperationDeniedException is defined in jena-core 
as a general point for access/permissions failures. The existing 
AddDeniedException is more general than access/permissions.  Having 
AccessDeniedException in jena-core means it can be caught (e.g. Fuseki) without 
a dependency on jena-permissions or any other specific access denial framework.

So {{UpdateDeniedException}} renamed as {{OperationDeniedException}}. Create 
{{AccessDeniedException}} extends {{OperationDeniedException}}.

>  rename the UpdateDeniedException
> ---------------------------------
>
>                 Key: JENA-990
>                 URL: https://issues.apache.org/jira/browse/JENA-990
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: Jena 3.0.0
>            Reporter: Claude Warren
>            Priority: Minor
>
> As noted in a discussion on the dev list between myself and Andy this update 
> is to rename the current UpdateDeniedException to AccessDeniedException and 
> extend it from a newly created OperationDeniedException.
> AddDeniedException and DeleteDeniedException will extend 
> AccessDeniedException.
> jena-permissions will extend AccessDeniedException to create:
> ReadDeniedException -- for read restrictions
> UpdateDeniedException -- for update restrictions (modifying triples that 
> already exists as opposed to adding new triples)
> This will allow Fuskei to properly respond to the case where jena-permissions 
> is in place and there are update restrictions in place.  Currently Fuseki 
> returns this as a 500 error.  Once we have a common permission denied 
> exception we can return either authentication required or access denied as 
> appropriate.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to