felix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r852502 - in /websites/staging/felix/trunk/content: ./ documentation/subprojects/apache-felix-framework/apache-felix-framework-usage-documentation.html
Date Fri, 01 Mar 2013 07:27:04 GMT
Author: buildbot
Date: Fri Mar  1 07:27:04 2013
New Revision: 852502

Log:
Staging update by buildbot for felix

Modified:
    websites/staging/felix/trunk/content/   (props changed)
    websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-usage-documentation.html

Propchange: websites/staging/felix/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Mar  1 07:27:04 2013
@@ -1 +1 @@
-1451152
+1451504

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-usage-documentation.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-usage-documentation.html
(original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-usage-documentation.html
Fri Mar  1 07:27:04 2013
@@ -76,16 +76,20 @@
       <h1>Apache Felix Framework Usage Documentation</h1>
       <h1 id="apache-felix-framework-usage-documentation">Apache Felix Framework Usage
Documentation</h1>
 <ul>
-<li><a href="">Downloading the Framework</a></li>
-<li><a href="">Starting the Framework</a></li>
-<li><a href="">Framework Shell</a>
-<strong> <a href="">Installing Bundles</a>
-</strong> <a href="">Web Proxy Issues when Installing Bundles</a></li>
-<li><a href="">Bundle Auto-Deploy</a></li>
-<li><a href="">Configuring the Framework</a>
-** <a href="">System Property Substitution</a></li>
-<li><a href="">Configuring Bundles</a></li>
-<li><a href="">Feedback</a></li>
+<li><a href="#downloading-the-framework">Downloading the Framework</a></li>
+<li><a href="#starting-the-framework">Starting the Framework</a></li>
+<li><a href="#framework-shell">Framework Shell</a><ul>
+<li><a href="#installing-bundles">Installing Bundles</a></li>
+<li><a href="#web-proxy-issues-when-installing-bundles">Web Proxy Issues when
Installing Bundles</a></li>
+</ul>
+</li>
+<li><a href="#bundle-auto-deploy">Bundle Auto-Deploy</a></li>
+<li><a href="#configuring-the-framework">Configuring the Framework</a><ul>
+<li><a href="#system-property-substitution">System Property Substitution</a></li>
+</ul>
+</li>
+<li><a href="#configuring-bundles">Configuring Bundles</a></li>
+<li><a href="#feedback">Feedback</a></li>
 </ul>
 <h2 id="downloading-the-framework">Downloading the Framework</h2>
 <p>Go to the <a href="">downloads</a> page and download the latest Felix
framework distribution.</p>
@@ -102,15 +106,26 @@
 
 <p>Where <code>&lt;cache-path&gt;</code> is the path you want to
use as the bundle cache. If you specify a relative cache path, then it will be treated as
relative to the current working directory.</p>
 <div class="info" markdown="1">
-**Useful Information**
-Previous versions of the framework prompted for a profile name when executed. The profile
name was used to create a directory inside `.felix/` in the user home directory. This approach
allowed users to have different sets of bundles for different purposes, e.g., testing, production,
etc. If this behavior is still desired, it is very easy to mimic. Modify `conf/config.properties`
to include "`felix.cache.rootdir=$\{user.home}/.felix`". Now, if you start Felix with something
like "`java -jar bin/felix.jar foo`", it will use "`$\{user.home}/.felix/foo/`" as the bundle
cache directory, where "`$\{user.home\`}" is automatically substituted with the appropriate
system property by the launcher.
+<b>Useful Information</b><br/>
+Previous versions of the framework prompted for a profile name when executed. The profile
name
+was used to create a directory inside <code>.felix/</code> in the user home directory.
This
+approach allowed users to have different sets of bundles for different purposes, e.g., testing,
+production, etc. If this behavior is still desired, it is very easy to mimic. Modify
+<code>conf/config.properties</code> to include "<code>felix.cache.rootdir=${user.home}/.felix</code>".
+Now, if you start Felix with something like "<code>java -jar bin/felix.jar foo</code>",
it will use
+"<code>${user.home}/.felix/foo/</code>" as the bundle cache directory, where
+"<code>${user.home}</code>" is automatically substituted with the appropriate
system property by
+the launcher.
 </div>
 
 <h2 id="framework-shell">Framework Shell</h2>
 <p>The main way to interact with the framework is via the supplied Apache Felix Gogo
shell. After starting the framework, type <code>help</code> into the shell to
see the list of the available commands and <code>help &lt;command-name&gt;</code>
to get help for a specific command.</p>
 <div class="info" markdown="1">
-**Useful Information**
-In Gogo, command names are made up of two parts: `<scope>:<name>`. This is similar
to a fully qualified class name in Java and is used to avoid naming collisions. If the `<name>`
portion of the command is unique, then you only need to type it. If not, then you must either
type the full `<scope>:<name>` or arrange the scope search path accordingly.
+<b>Useful Information</b><br/>
+In Gogo, command names are made up of two parts: <code>&lt;scope&gt;:&lt;name&gt;</code>.
This is similar
+to a fully qualified class name in Java and is used to avoid naming collisions. If the
+<code>&lt;name&gt;</code> portion of the command is unique, then you
only need to type it. If not,
+then you must either type the full <code>&lt;scope&gt;:&lt;name&gt;</code>
or arrange the scope search path accordingly.
 </div>
 
 <p>To install bundles, use the <code>felix:install</code> command, which
is described in more detail in the next <a href="">sub-section</a>. To list installed
bundles, use the <code>felix:lb</code> command. To stop the framework type <code>stop
0</code> to stop the System Bundle; any installed bundles will automatically be reloaded
(and potentially restarted) the next time you launch with the associated cache.</p>
@@ -142,8 +157,13 @@ In Gogo, command names are made up of tw
 <p>The <code>felix:stop</code> command is used to stop a bundle and the
<code>felix:uninstall</code> command is used to remove a bundle from the bundle
cache. As an alternative to using the <code>felix:install</code> and <code>felix:start</code>
commands explicitly, it is also possible to install and start a bundle in one step by using
the <code>felix:start</code> command with a bundle URL.</p>
 <p>Bundles can be updated using the <code>felix:update</code> command.
The update command allows you to specify an URL from which to retrieve the updated bundle,
but if one is not specified it will try to update the bundle from the bundle's <code>Bundle-UpdateLocation</code>
manifest attribute, if present, or the bundle's original location URL.</p>
 <div class="info" markdown="1">
-**Useful Information**
-When you use `felix:update` or `felix:uninstall`, the changes appear to take effect immediately,
but in reality the changes are only partially enacted. If a bundle is updated or uninstalled
and it was exporting packages, these packages are not removed until the framework is refreshed
using the `PackageAdmin` service. The Felix shell offers a convenient `refresh` command for
this purpose. This is the correct behavior as defined by the OSGi specification.
+<b>Useful Information</b><br/>
+When you use <code>felix:update</code> or <code>felix:uninstall</code>,
the changes appear to take
+effect immediately, but in reality the changes are only partially enacted. If a bundle is
updated
+or uninstalled and it was exporting packages, these packages are not removed until the framework
+is refreshed using the <code>PackageAdmin</code> service. The Felix shell offers
a convenient
+<code>refresh</code> command for this purpose. This is the correct behavior as
defined by the OSGi
+specification.
 </div>
 
 <p>For an introduction to writing bundles and services, refer to the Felix bundle tutorial.</p>
@@ -184,7 +204,7 @@ When you use `felix:update` or `felix:un
 <h2 id="feedback">Feedback</h2>
 <p>Subscribe to the Felix users mailing list by sending a message to <a href="">users-subscribe@felix.apache.org</a>;
after subscribing, email questions or feedback to [users@felix.apache.org|mailto:users@felix.apache.org].</p>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1422427 by fmeschbe on Sun, 16 Dec 2012 00:36:51 +0000
+        Rev. 1451504 by fmeschbe on Fri, 1 Mar 2013 07:26:51 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project



Mime
View raw message