On Mon, May 26, 2014 at 6:58 PM, Antonio David Perez Morales <ape...@zaizi.com> wrote: > Hi Florent, Rupert and all > > I have already created two new issues as sub-tasks of Stanbol-1008 ([1] and > [2]) > The first one intends to integrate the current Florent's approach into > Stanbol 1.0 to see if it works well. > The second one is about to add support to new routes deployed either as > bundles, either XML files put in a specific folder (containing routes and > loaded dynamically) or (if necessary) via a new REST endpoint receiving > XML route files to be loaded (or removed). >
Make sure to evaluate the Apache Sling Installer [3] and/or the Felix File Installer [4] both can be extended to support custom artifacts (such as XML route files). > I think this can be a good advance for the midterm. This way (and > leveraging the engine camel component created by Florent) we would have > covered the current Enhancement Chain execution process using Camel routes. > Well, more powerful because all the existing Camel components could be used > in the routes to perform advanced (or parallel) processing. > > How do you see it guys? > > Taking into account that the second part of the GSoC is longer than the > first one, I would like to open a discussion about the new Camel components > to be created in the second part in order to be used in routes (apart from > improve the current engine component already developed). As discussed in > previous messages some interesting components could be: > - chain: In order to create routes based on existing chains +1 > - store: To store the result in EntityHub or another store 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 > - other components > > But I would like to sort them by importance of need based on interesting > use cases like: > - Fetch from : local folder / rss / mail / ... > - Enhance with engine 1 > - Depending on the result of this engine go to : > - Chain 1 > - or to Chain 2 and 3 and merge results > - Output the result to : email / ftp / ... and contenthub > > Do you have any interesting use cases in mind which would be good to have > in Stanbol? In this way, we can decide which components should be developed > first. A strong use-case - possibly Enterprise Integration alike - would be cool. best Rupert > [1] https://issues.apache.org/jira/browse/STANBOL-1347 > [2] https://issues.apache.org/jira/browse/STANBOL-1348 [3] http://sling.apache.org/documentation/bundles/osgi-installer.html [4] http://felix.apache.org/site/apache-felix-file-install.html -- | Rupert Westenthaler rupert.westentha...@gmail.com | Bodenlehenstraße 11 ++43-699-11108907 | A-5500 Bischofshofen | REDLINK.CO .......................................................................... | http://redlink.co/
