Hi Rupert On Tue, May 27, 2014 at 8:51 AM, Rupert Westenthaler < rupert.westentha...@gmail.com> wrote:
> 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 will take a look at it (before creating a specific monitor in a folder with Java WatchService) after testing (and adapting if necessary) the current Florent's code to the 1.0 version. > > 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. > What I meant is that we can create components to deal with EntityHub (getting and putting entities) and use that component in other routes (inside or outside Stanbol) > > - 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 > Yes Rupert, it was only an idea about what we can achieve integrating Camel and developing new components. > - 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. > > Perfect, so I will start with the first issue to integrate the current trial into 1.0 and then will take a look at [3] and [4] to see if it can fit to deploy new routes in XML (for Java routes we will use bundles). After that, we can decide the best components to be deployed first. Regards -- ------------------------------ 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.
