You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "christopher james dollin (JIRA)" <ji...@apache.org> on 2011/03/23 14:37:06 UTC
[jira] [Commented] (JENA-50)
com.hp.hpl.jena.util.ResourceUtils.renameResource(Resource, String) rebinds
Graph even if no changes were made
[ https://issues.apache.org/jira/browse/JENA-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010118#comment-13010118 ]
christopher james dollin commented on JENA-50:
----------------------------------------------
The previous code contained a concurrent modification bug, not visible when using the usual memory model but visible using eg SmallGraphMem. Added a test using that to expose the issue. Rewrote renameResource retaining the principle of working at the non-inference-graph level but simplifying heavily. There is no need to have a special check for the possible reflexive triples -- duplicates will be eliminated when the new triples are
added to the graph.
> com.hp.hpl.jena.util.ResourceUtils.renameResource(Resource, String) rebinds Graph even if no changes were made
> --------------------------------------------------------------------------------------------------------------
>
> Key: JENA-50
> URL: https://issues.apache.org/jira/browse/JENA-50
> Project: Jena
> Issue Type: Bug
> Components: Jena
> Environment: all
> Reporter: Thorsten Möller
> Assignee: christopher james dollin
> Priority: Minor
> Attachments: Jena.patch
>
>
> This issue directly goes back to the following patch
> http://sourceforge.net/tracker/index.php?func=detail&aid=3046428&group_id=40417&atid=430290
> The underlying Graph is rebound even in (rare) cases where the Graph is actually not modified by the method (e.g., there is a Resource to be renamed but there is actually no triple in the model that involves it).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira