You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by bu...@apache.org on 2012/10/25 14:19:15 UTC
svn commit: r836134 - in /websites/staging/stanbol/trunk/content: ./
production/file-bundle-configuration.html production/partial-updates.html
production/your-launcher.html
Author: buildbot
Date: Thu Oct 25 12:19:15 2012
New Revision: 836134
Log:
Staging update by buildbot for stanbol
Modified:
websites/staging/stanbol/trunk/content/ (props changed)
websites/staging/stanbol/trunk/content/production/file-bundle-configuration.html
websites/staging/stanbol/trunk/content/production/partial-updates.html
websites/staging/stanbol/trunk/content/production/your-launcher.html
Propchange: websites/staging/stanbol/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Oct 25 12:19:15 2012
@@ -1 +1 @@
-1402121
+1402126
Modified: websites/staging/stanbol/trunk/content/production/file-bundle-configuration.html
==============================================================================
--- websites/staging/stanbol/trunk/content/production/file-bundle-configuration.html (original)
+++ websites/staging/stanbol/trunk/content/production/file-bundle-configuration.html Thu Oct 25 12:19:15 2012
@@ -102,18 +102,28 @@ Stanbol offer the <strong>bundleconfig</
|- config2.conf
|- ....
</pre></p>
-<p>The pom.xml has nothing special. You can copy <a href="https://svn.apache.org/repos/asf/stanbol/trunk/data/defaultconfig/pom.xml">this one</a> for example and only adapt group and artifact ID to suit your project naming convention.
-The configurations are held by files in the src/main/resources/config folder. This configurations files :
-<em> need to respect this naming convention :
- * {bundleArtifactID}-{uniqueID}.conf, where {uniqueID} can be anything but unique to not be overloaded.
- * for example a configuration file with this name "org.apache.stanbol.enhancer.engines.keywordextraction.engine.KeywordLinkingEngine-entityhub.config" will be used to configure the Keyword Linking Engine bundle.
-</em> contains key-values pairs lines where :
- * the key is the fully qualified name of the property (example : org.apache.stanbol.enhancer.engines.keywordextraction.maxSuggestions)
- * and the value is a string that contains the needed value for the property. To ensure a correct binding between the value in the configuration file and the property's Java type, this conventions are helpfull :
- * <em>"my value"</em> : for String properties
- * <em>B"false"</em> : for boolean properties
- * <em>I"5"</em> : for int properties
- * <em>["value1","value2"]</em> : for String collection properties</p>
+<p>The pom.xml has nothing special. You can copy <a href="https://svn.apache.org/repos/asf/stanbol/trunk/data/defaultconfig/pom.xml">this one</a> for example and only adapt group and artifact ID to suit your project naming convention.<br />
+</p>
+<p>The configurations are held by files in the src/main/resources/config folder. This configurations files :<br />
+</p>
+<ul>
+<li>need to respect this naming convention :<ul>
+<li>{bundleArtifactID}-{uniqueID}.conf, where {uniqueID} can be anything but unique to not be overloaded.</li>
+<li>for example a configuration file with this name "org.apache.stanbol.enhancer.engines.keywordextraction.engine.KeywordLinkingEngine-entityhub.config" will be used to configure the Keyword Linking Engine bundle.</li>
+</ul>
+</li>
+<li>contains key-values pairs lines where : <ul>
+<li>the key is the fully qualified name of the property (example : org.apache.stanbol.enhancer.engines.keywordextraction.maxSuggestions)</li>
+<li>and the value is a string that contains the needed value for the property. To ensure a correct binding between the value in the configuration file and the property's Java type, this conventions are helpfull :<ul>
+<li><em>"my value"</em> : for String properties</li>
+<li><em>B"false"</em> : for boolean properties</li>
+<li><em>I"5"</em> : for int properties</li>
+<li><em>["value1","value2"]</em> : for String collection properties</li>
+</ul>
+</li>
+</ul>
+</li>
+</ul>
<p>Of course, this bundleconfig bundle can be added to your <a href="your-launcher.html">custom launcher and bundlelist</a>, just be careful to define a higher startlevel to your bundleconfig than the configured bundles' startlevel.</p>
</div>
Modified: websites/staging/stanbol/trunk/content/production/partial-updates.html
==============================================================================
--- websites/staging/stanbol/trunk/content/production/partial-updates.html (original)
+++ websites/staging/stanbol/trunk/content/production/partial-updates.html Thu Oct 25 12:19:15 2012
@@ -91,9 +91,24 @@ Felix web interface allow you to do this
The Apache Sling File Provider allow you to define a folder, where you just have to drop/update/delete your bundle to get your server in sync.<br />
</p>
<p>Follow this two step procedure to enjoy this feature :<br />
-<em> 0. Install the "Sling File Provider" Bundle (not needed as this is included by default in Stanbol)
-</em> 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 on you file system.</p>
+</p>
+<ul>
+<li>
+<ol>
+<li>Install the "Sling File Provider" Bundle (not needed as this is included by default in Stanbol)</li>
+</ol>
+</li>
+<li>
+<ol>
+<li>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.</li>
+</ol>
+</li>
+<li>
+<ol>
+<li>Create the referenced Folder on you file system.</li>
+</ol>
+</li>
+</ul>
<p>Note : this procedure was extracted for a Rupert Westenthaler's <a href="http://markmail.org/message/jpxpl6x4nkmz6kda">mail</a>. Thanks to him to spot it !</p>
</div>
Modified: websites/staging/stanbol/trunk/content/production/your-launcher.html
==============================================================================
--- websites/staging/stanbol/trunk/content/production/your-launcher.html (original)
+++ websites/staging/stanbol/trunk/content/production/your-launcher.html Thu Oct 25 12:19:15 2012
@@ -99,15 +99,14 @@ But identify and manually add all featur
<li>Bundlelist are in fact just jar. So you just need to declare them as dependencies in you launcher pom.xml to get the feature package and all required bundle for it.</li>
<li>
<p>For example, if you want the entityHub feature in you server, you only need to add this dependency to your launcher pom.xml :
-<pre>
- <dependency>
- <groupId>org.apache.stanbol</groupId>
- <artifactId>org.apache.stanbol.entityhub.bundlelist</artifactId>
- <version>0.11.0-SNAPSHOT</version>
- <type>partialbundlelist</type>
- <scope>provided</scope>
- </dependency>
-</pre></p>
+<code>xml
+ <dependency>
+ <groupId>org.apache.stanbol</groupId>
+ <artifactId>org.apache.stanbol.entityhub.bundlelist</artifactId>
+ <version>0.11.0-SNAPSHOT</version>
+ <type>partialbundlelist</type>
+ <scope>provided</scope>
+ </dependency></code></p>
</li>
<li>
<p>Please note the <pre><type>partialbundlelist</type></pre> property of the dependency.</p>
@@ -154,25 +153,27 @@ But identify and manually add all featur
<p>The bundlelist mechanism is the perfect and simple way to include your list of bundles into your launcher ! </p>
</li>
</ul>
-<h2 id="build-your-bundlelist-dependency">Build <em>your</em>* bundlelist dependency</h2>
+<h2 id="build-your-bundlelist-dependency">Build <em>your</em> bundlelist dependency</h2>
<ul>
<li>
-<p>Bundlelist (or partialbundlelist) artifact is a really simple Maven project that rely on this structure :</p>
-<p>mybundlelistFolder
- |
- |- pom.xml
- |- src
- |- main
- |- bundles
- |- list.xml</p>
+<p>Bundlelist (or partialbundlelist) artifact is a really simple Maven project that rely on this structure :
+<pre>
+ mybundlelistFolder
+ |
+ |- pom.xml
+ |- src
+ |- main
+ |- bundles
+ |- list.xml
+</pre></p>
</li>
<li>
<p>You only need to define 2 files : </p>
<ul>
<li>pom.xml : really simple you can copy-paste the <a href="http://svn.apache.org/repos/asf/stanbol/trunk/enhancer/bundlelist/pom.xml">Enhancer bundlelist</a> one and only change the groupId and artifactId properties to suit you need. All the magic here is contained in <packaging> property.</li>
-<li>list.xml : this file will contains information about the bundles you want to include. This file has a simple structure :</li>
-</ul>
-<p><bundles>
+<li>list.xml : this file will contains information about the bundles you want to include. This file has a simple structure :
+<pre><code>
+<bundles>
<startlevel level="L0">
<bundle>
...Maven groupId,artifactID and version properties...
@@ -184,7 +185,9 @@ But identify and manually add all featur
<startlevel level="L1">
... anothers bundles nodes...
</startlevel>
-</bundles></p>
+</bundles>
+<code></pre></li>
+</ul>
</li>
<li>
<p>Start level is an important things to keep in mind as the value of the "level" property will determine when your bundle is started during the server launch.</p>