-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ahh-- I believe that would be it. There's no way with my current experiment that the config could get loaded. Well, live and learn. Today I learned something about manually building up Yards and Indexes!
I'll get that config incorporated in the next try. Thanks! Some questions I feel emboldened to ask: would it perhaps be better for that "startup config" to be associated with the EntityHub service itself (and not the launchers), or would that be too direct a dependence? I can certainly imagine wanting to use a Clerezza Yard instead, or a remote Solr instance, or some other arrangement, but might it not be better to have everything the EntityHub service needs come with the bundlelist/feature repository itself? - --- A. Soroka Software & Systems Engineering :: Online Library Environment the University of Virginia Library On Mar 6, 2012, at 4:49 PM, Rupert Westenthaler wrote: > > On 06.03.2012, at 21:09, [email protected] wrote: > >> 5) After getting the Stanbol Commons and EntityHub up and started, I had to >> manually configure the EntityHub's own Yard. This wasn't difficult, but it's >> not totally clear to me why the bundles didn't do this on activation. > > The configuration of the SolrYard used by the Entityhub itself is provided by > the default configuration of the Sling launcher. > > > http://svn.apache.org/repos/asf/incubator/stanbol/trunk/launchers/stable/src/main/resources/resources/config/org.apache.stanbol.entityhub.yard.solr.impl.SolrYard-entityhub.config > > Are you sure that the configurations included in the Sling Launcher are > loaded by Karaf? > > best > Rupert -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJPVoqRAAoJEATpPYSyaoIk7WAIAKZLxXEkKUUBpe6DGUmot1OW cWM/uoDLtBaBLtGrrfo0stNnbbS/5RnqKLFXPoowYn1lS+LYKxw3H0EAIvUanUWS xwz0CAzoEkcQHCyeY2vTQ/IqnHxjq5Uc1JgsY683TGr7EzxTX4eoXTTO1QwCfqtT GdLqtoqYpkezU2Pnsf8QTj9c6woPUpj1tRmmvmkIqF41P2LGFSnHq3uBMdfEbQKx Fvsnk5Dp1lzq15WtIz3v8hjQ/tVzw9jpwRuFeaJ0u0wRAjUYXPJLFqcCZDVrDBAw UHrm9ieMp/ERnURB2KoELqTeFoQWS/6CU9sHPqH14brTZyfKCWr5ldBilQPKtVE= =9YOd -----END PGP SIGNATURE-----
