Hi people I have already started to work on [1] to integrate current Florent's code into Stanbol 1.0. As a first approach, only changing the dependency versions to new Stanbol 1.0, many issues have arisen: - Deprecated use of classes - Classes which have changed from package - Some classes not necessary now - Classes not used which were causing conflicts - ...
So now I'm trying to resolve all these problems to replicate the same behavior from 0.9 into 1.0. I will upload the code to a Github repository in my account (which will be pushed later into a Stanbol branch after the project) in order to track the advances. Once I can resolve all these problems, I will take a look to the Felix Custom Artifacts poiinted out by Rupert in a previous message to find out the best way to deploy (and manage) route configurations (felix artifacts, watchservice java, rest endpoint to receive xml routes, etc). Comments on this and future tasks are more than welcome. Regards [1] https://issues.apache.org/jira/browse/STANBOL-1347 On Tue, May 27, 2014 at 9:53 AM, Rafa Haro <rh...@apache.org> wrote: > Hi Rupert, Florent and Antonio > > El 27/05/14 08:51, Rupert Westenthaler escribió: > > As the result of Enhancement Routes is content + metadata I can not >> see what you want to "store" in the Entityhub that is about managing >> Entities. >> >> > - entityhub: To query/update the entityhub component >>> >> Maybe. If you can come up with a good use case ^^ >> >> > - contenthub: To develop a new content-hub using chain/engine >>> components >>> >and solr/elasticsearch/whatever component (solr and elasticsearch >>> component >>> >already exist in Camel) >>> >> IMO implementing a new Contenthub like component is outside the scope >> of this GSoC project. However If there is already Solr/Elasticsearch >> component it would be a really useful thing >> >> > Regarding this, in my opinion, the use case of an eventual integration > with a Content hub is probably one of the most clear for this project. I'm > not sure if that is what Antonio was trying to explain but, with a single > route using as last endpoint Solr or any other backend system, we would be > almost cloning the same functionality than the previous ContentHub > implementation (Stanbol 0.12). Entities could be dereferenced using the > EntityHub before storing the content along with the metadata, which is the > point of integration of the EntityHub in such use case. And even most > interesting, now with the integration of Marmotta contributed by Rupert, it > would be possible to use a whole graph for dereferencing, so "simply" > routing components like Enhancer->Marmotta->Solr sounds to me like an > interesting use case. > > wdyt? > > Cheers, > Rafa > -- ------------------------------ This message should be regarded as confidential. If you have received this email in error please notify the sender and destroy it immediately. Statements of intent shall only become binding when confirmed in hard copy by an authorised signatory. Zaizi Ltd is registered in England and Wales with the registration number 6440931. The Registered Office is Brook House, 229 Shepherds Bush Road, London W6 7AN.
