anukat2015 / elda

Automatically exported from code.google.com/p/elda
0 stars 0 forks source link

Running multiple api specs on one elda instance #148

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Hi, 

is it possible to run one instance of elda with multiple specs?

Running 

  java -jar elda-standalone-1.2.8.jar -Delda.spec=test.ttl,education.ttl

sets up the api specified in test.ttl neatly, and the education api is also 
successfully loaded and elda endpoints registered as far as I can see in the 
log, however, going to

  http://localhost:8080/elda/api/education/schools

gives me

DEBUG [qtp4815156-19] (RouterRestlet.java:325) - Failed to return results: 
Could not find anything matching /education/schools...

Original issue reported on code.google.com by m.g.skja...@gmail.com on 30 Mar 2012 at 12:07

GoogleCodeExporter commented 8 years ago
You can run multiple.

Elda does not warn you when one spec file in the chain CRASHES the chain loader 
for the spec files.

imagine: config1.ttl,config2.ttl,config3.ttl
if config2.ttl has an error and is loaded second, nothing else loads, and there 
is nothing in the logs (that I could see) about which spec file had the error 
in it.

Maybe this needs to be a 'config loading' change request to ELDA's default 
behavior.

Terry

Original comment by terry.ra...@gmail.com on 11 Apr 2012 at 7:30

GoogleCodeExporter commented 8 years ago

Original comment by ehog.he...@googlemail.com on 17 Apr 2012 at 2:26

GoogleCodeExporter commented 8 years ago
From 1.2.12 (possibly earlier), there's an INFO log before trying to load a 
config,
so if there's a crash it should be due to the most recent load.

Original comment by ehog.he...@googlemail.com on 28 May 2012 at 12:48

GoogleCodeExporter commented 8 years ago
Just doubled-checked with 1.2.13-SNAPSHOT (which is functionally equal to 
1.2.12 in this area) and had no trouble loading up two specs and accessing 
their endpoints
with

 java -jar elda-standalone-1.2.8.jar -Delda.spec=SPEC1,SPEC2

(where SPEC[12] were in the current directory and referred to as ../SPEC[12] as
appropriate.) 

I shall close this issue absent further problem reports.

Original comment by ehog.he...@googlemail.com on 28 May 2012 at 2:12