Hi On Thu, Aug 2, 2012 at 3:04 AM, harish suvarna <[email protected]> wrote: > Removing the stanbol folder in the trunk helped me. This stanbol folder is > created by the build process.
Generally: The first time you start Stanbol (and the /stanbol folder is created) the jar files (bundles) , configurations ... are copied from the runnable jar. On any further start the copied information are used. Therefore replacing the launcher jar will not have any effect! To update a component (e.g. an Engine) you need to use the "install/update" the according Bundle(s). This can be done by several different ways (e.g. by going to "http://{stanbol}/system/console/bundles"; and using the '[install/update...]' button.) You can also use the Sling Maven Plugin [1] or configure the Sling File Provider [2]. As there is no documentation here the needed steps to setup the Sling File Provider 0) Install the "Sling File Provider" Bundle (not needed as this is included by default) 1) Configure the "sling.fileinstall.dir" property: You can add this to the "{stanbol-working-dir}/stanbol/sling.properties file" or parse it as a system property '-Dsling.fileinstall.dir={path-to-dir}' when you start stanbol. 2) Create the referenced Folder After that the "Sling File Provider" will automatically install/update/delete bundles and configurations added/updated/deleted in that folder. [1] http://sling.apache.org/site/sling.html [2] http://svn.apache.org/repos/asf/sling/tags/org.apache.sling.installer.provider.file-1.0.2 > Thanks a lot for the help. > > In general, if we have a custom jar file how do we integrate into stanbol? > Does stanbol allow this? You can install OSGI bundles by using the Felix Web Console (as described above). Jar files that are no Bundles can not be added to Stanbol. best Rupert -- | Rupert Westenthaler [email protected] | Bodenlehenstraße 11 ++43-699-11108907 | A-5500 Bischofshofen
