[
https://issues.apache.org/jira/browse/CLEREZZA-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918540#action_12918540
]
Reto Bachmann-Gmür commented on CLEREZZA-316:
---------------------------------------------
In one of the patches I see:
- systemGraph.add(new TripleImpl(instance, PLATFORM.languages,
- listNode));
+ Lock writeLock = systemGraph.getLock().writeLock();
+ writeLock.lock();
+ try {
+ systemGraph.add(new TripleImpl(instance,
PLATFORM.languages, listNode));
+ } finally {
+ writeLock.unlock();
+ }
why this?
> Update where a GraphNode accessible in ssp bases on a graph injected with
> service
> ---------------------------------------------------------------------------------
>
> Key: CLEREZZA-316
> URL: https://issues.apache.org/jira/browse/CLEREZZA-316
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Tsuyoshi Ito
> Assignee: Manuel Innerhofer
>
> Fix if this can easily be prevented
>
> Possibly: have a service returning an unsecured graph, maybe add a method
> getUnsecuredMGrah to SecuredMGraph, this method would check permissions while
> the retuned mgarph would no longer need to. => to do in a dedicated issue
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
