You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2015/07/23 10:35:05 UTC
[jira] [Resolved] (JENA-990) rename the UpdateDeniedException
[ https://issues.apache.org/jira/browse/JENA-990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Seaborne resolved JENA-990.
--------------------------------
Resolution: Fixed
Fix Version/s: Jena 3.0.0
> 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
> Assignee: Claude Warren
> Priority: Minor
> Fix For: Jena 3.0.0
>
>
> 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)