On 27 August 2014 12:37, Reto Gmür <[email protected]> wrote: > > As I wrote, having the component taking care of accessing the triple store > by being individually configured to use a sparql endpoint is nonsense in my > opinion. Using a hardcoded default password even more. > > > In the short term, this is the easiest way of getting my app running in the Fusepool/Stanbol environment. Later I can look at accessing the TcManager through OSGi, for sure. But while auth issues are a big complication, I don't see any problem with the general idea in principle.
What do you mean by totally remote? A Sparql enpoint accessed via HTTP is > remote by default. > Running on a seperate server, outside of the OSGi environment. There would be certain advantages to this, splitting up the workload being the big one. And disadvantages, like the auth stuff. > > > Are you using any clerezza features? If you just need the SPARQl endpoint > it might be more straight forward to have a separate application in its own > OSGi container. It's a bit further down the road, but I want to be able to make use of Stanbol for entity extraction, enhancement etc. Link the data NewsMonitor pulls in with other content, throw it in the pool. But as you say, having a separate application is another option. Maven profiles might be able to help there. Ceers, Danny.
