On Wed, Aug 27, 2014 at 4:13 PM, Danny Ayers <[email protected]> wrote:
> 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. > Again, if you are accessing graphs available via TcManager you should not use HTTP. The distribution that you can have the triple store on a "totally remote" server is provided by TcManager. The app should not care about this. What you are doing is like not taking the stairs in the building, but exiting though the window and accessing the first floor with a ladder. Of course not without having disabled the alarm before leaving the building and breaking into the first floor. > > > > > > > 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. > I would not recommend maven profiles to create different apps. Rather I'd recommend to have different maven projects, e.g. "commons", "standalone" and "bundle", the bulk of the code would be in "commons", "bundle" would provide the few lines to place a query via TcManager and "standalone" would provide some more lines to make a remote request and parse the result. Obvioulsy one pom creates a runnable jar and another a deployable bundle. Cheers, Reto > > Ceers, > Danny. >
