[
https://issues.apache.org/jira/browse/STANBOL-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282032#comment-13282032
]
Peter Ansell commented on STANBOL-621:
--------------------------------------
There will also need to be some changes in Clerezza before this issue can be
fixed, as the Dataset and DatasetGraph APIs contain some new methods. I patched
them roughly yesterday on my clerezza fork on Github
https://github.com/ansell/clerezza/commit/37747324d980fad6a33caa3da00491da66900c37
(Note, that commit ID may not always be up to date as I rebase regularly) Note
also that I have purged most of Clerezza out of my fork as I didn't actually
need to use the real parts of clerezza, just the rdf utilities.
There was also a failing test with TdbMGraphTest that I didn't understand
completely. It appeared that the getEmptyMGraph method in tests was not
returning a new empty TdbMGraph each time, so I worked around that by modifying
the tests so that they were independent, and that the empty check happened
everytime getEmptyMGraph was called (by delegating to a new abstract
getEmptyMGraphImplementation method)
> Upgrade to Apache Jena
> ----------------------
>
> Key: STANBOL-621
> URL: https://issues.apache.org/jira/browse/STANBOL-621
> Project: Stanbol
> Issue Type: Improvement
> Affects Versions: 0.10.0-incubating
> Reporter: Peter Ansell
> Assignee: Rupert Westenthaler
> Attachments: upgradejena.diff
>
>
> Apache Jena released its first version, and should be used in preference to
> 2.6.3 (released June 2010).
> Jena 2.7.0-incubating has SPARQL 1.1 functionality that can replace some of
> the custom functions that were in use, including createURI and concat.
> The patch attached to this issue converts to org.apache.jena where necessary,
> including adding the jena-larq package (as it was split off since the last
> version that was in use) and removing two custom functions that are included
> in SPARQL 1.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
