[
https://issues.apache.org/jira/browse/STANBOL-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rupert Westenthaler reopened STANBOL-1170:
------------------------------------------
Reopen because of the problem described by [1]. After refactoring the
`clerezza.SparqlFieldQueryFactory`extends `sparql.SparqlFieldQuery` instead of
`sparql.SparqlFieldQueryFactory`.
Basically a typo that is causing the backward incompatibility.
Big thanks to Reto for reporting.
[1]
http://mail-archives.apache.org/mod_mbox/stanbol-dev/201310.mbox/%3CCALvhUEW8mf0URO8zPBmOzVmti%2Bjqusxa6h7KFK7KwkbNWXW7nQ%40mail.gmail.com%3E
> Refactor entityhub.query.clerezza module
> ----------------------------------------
>
> Key: STANBOL-1170
> URL: https://issues.apache.org/jira/browse/STANBOL-1170
> Project: Stanbol
> Issue Type: Sub-task
> Components: Entityhub
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
>
> The entityhub.query.clerezza module currently contains the
> 1. FieldQuery to SPARQL mappings
> 2. Clerezza specific implementations and utilities for ResultLists ....
> For the implementation of the SesameYard (1) is required, but a dependency to
> Clerezza is sub-optimal.
> Because of that all SPARQL generic features should be extracted to a new
> entityhub.query.sparql module. Clerezza specific extensions should stay in
> the entityhub.query.clerezza module. Maybe also introduce a
> entityhub.query.sesame module with similar functionality as the clerezza one.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
