sling-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dk...@apache.org
Subject svn commit: r1529997 - in /sling/site/trunk/content: old-stuff/assembly.mdtext site/.htaccess site/assembly.html site/client-request-logging.html
Date Mon, 07 Oct 2013 16:57:51 GMT
Author: dklco
Date: Mon Oct  7 16:57:51 2013
New Revision: 1529997

URL: http://svn.apache.org/r1529997
Log:
Working on translating the assembly page

Removed:
    sling/site/trunk/content/site/assembly.html
    sling/site/trunk/content/site/client-request-logging.html
Modified:
    sling/site/trunk/content/old-stuff/assembly.mdtext
    sling/site/trunk/content/site/.htaccess

Modified: sling/site/trunk/content/old-stuff/assembly.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/old-stuff/assembly.mdtext?rev=1529997&r1=1529996&r2=1529997&view=diff
==============================================================================
--- sling/site/trunk/content/old-stuff/assembly.mdtext (original)
+++ sling/site/trunk/content/old-stuff/assembly.mdtext Mon Oct  7 16:57:51 2013
@@ -1,9 +1,6 @@
-translation_pending: true
 Title: Assembly
 
-{panel}
 The Assembly concept grew out of a need to bundle together a set of OSGi Bundles to deploy
applications. The concept has been developped before the OSGi Deployment Package Service Specification
has been published in the Release 4.1 Compendium Services Specification. It will have to be
discussed whether the Assembly concept is dropped in favor of the Deplyoment Package Service.
-{panel}
 
 ## Introduction
 
@@ -35,8 +32,8 @@ Assemblies are managed by the *Assembly 
 
 As an Assembly is a standard Bundle, all the defined Bundle manifest headers may be specified.
In addition, for the *Assembly Manager* to recognize an assembly and for the OSGi Bundle Repository
to support dependency resolution, the following manifest headers are defined. All headers
are optional with documented default values except where noted.
 
-* *Assembly-Bundles* - The list of bundles contained in this assembly. See below for the
definition of the syntax of this header. This header is required. The presence of this headers
identifies an Assembly to the *Assembly Manager*.
-* *Assembly-BundleRepository* - A comma-separated list of URLs pointing to OSGi Bundle Repository
descriptors. These bundle repositories will be used to install bundles listed in the `Assembly-Bundles`
header. This header is optional with not default value.
+* **Assembly-Bundles** - The list of bundles contained in this assembly. See below for the
definition of the syntax of this header. This header is required. The presence of this headers
identifies an Assembly to the *Assembly Manager*.
+* **Assembly-BundleRepository** - A comma-separated list of URLs pointing to OSGi Bundle
Repository descriptors. These bundle repositories will be used to install bundles listed in
the `Assembly-Bundles` header. This header is optional with not default value.
 
 
 
@@ -44,13 +41,13 @@ As an Assembly is a standard Bundle, all
 
 An Assembly, like all bundles, may be in any of the defined bundle states:
 
-* *Installed* - The Assembly bundle has been installed into the system but not yet resolved.
The *Assembly Manager* will try to install all bundles listed in the `Assembly-Bundles` header.
The start levels of the bundles will be set according to the `startlevel` parameter. The bundles
will not be started. If installation of one or more of the bundles fails, *Assembly Manager*
logs an error message.
-* *Resolved* - The Assembly bundle is resolved, that is all imported packages are wired into
the framework. The *Assembly Manager* does not handle this state change, rather the installed
bundles will be resolved by the framework either automatically after installation or when
started later.
-* *Started* - The Assembly bundle has been started by calling the `Bundle.start()` method.
The *Assembly Manager* will start all newly installed and resolved bundles. Depending on the
start level set on the bundle(s) and the current system start level, the bundles will only
be permanently marked to start while actually starting the bundles may be delayed until the
system enters the respective start level. If any bundle fails to start, an error message is
logged.
-* *Stopped* - The Assembly bundle has been stopped by calling the `Bundle.stop()` method.
All bundles belong to the Assembly and linked to the Assembly are also stopped.
-* *Unresolved* - The Assembly bundle has been unresolved by the system for any reason, possibly
any missing dependencies. Assembly bundles entering this state are ignored by the *Assembly
Manager*.
-* *Uninstalled* - The Assembly bundle is being uninstalled by calling the `Bundle.uninstall()`
method. The *Assembly Manager* will (try to) uninstall all bundles listed in the `Assembly-Bundles`
header.
-* *Updated* - The Assembly bundle will update all bundles installed previously according
to the `Assembly-Bundles` header. If this header omits any bundle listed in the previous bundle
version, the respective bundle is uninstalled from the system. If a bundle is already installed
with the correct version, the installed bundle is not touched (It may though be uninstalled
together with the Assembly Bundle if the Assembly Bundle is uninstalled).
+* **Installed** - The Assembly bundle has been installed into the system but not yet resolved.
The *Assembly Manager* will try to install all bundles listed in the `Assembly-Bundles` header.
The start levels of the bundles will be set according to the `startlevel` parameter. The bundles
will not be started. If installation of one or more of the bundles fails, *Assembly Manager*
logs an error message.
+* **Resolved** - The Assembly bundle is resolved, that is all imported packages are wired
into the framework. The *Assembly Manager* does not handle this state change, rather the installed
bundles will be resolved by the framework either automatically after installation or when
started later.
+* **Started** - The Assembly bundle has been started by calling the `Bundle.start()` method.
The *Assembly Manager* will start all newly installed and resolved bundles. Depending on the
start level set on the bundle(s) and the current system start level, the bundles will only
be permanently marked to start while actually starting the bundles may be delayed until the
system enters the respective start level. If any bundle fails to start, an error message is
logged.
+* **Stopped** - The Assembly bundle has been stopped by calling the `Bundle.stop()` method.
All bundles belong to the Assembly and linked to the Assembly are also stopped.
+* **Unresolved** - The Assembly bundle has been unresolved by the system for any reason,
possibly any missing dependencies. Assembly bundles entering this state are ignored by the
*Assembly Manager*.
+* **Uninstalled** - The Assembly bundle is being uninstalled by calling the `Bundle.uninstall()`
method. The *Assembly Manager* will (try to) uninstall all bundles listed in the `Assembly-Bundles`
header.
+* **Updated** - The Assembly bundle will update all bundles installed previously according
to the `Assembly-Bundles` header. If this header omits any bundle listed in the previous bundle
version, the respective bundle is uninstalled from the system. If a bundle is already installed
with the correct version, the installed bundle is not touched (It may though be uninstalled
together with the Assembly Bundle if the Assembly Bundle is uninstalled).
 
 
 
@@ -81,10 +78,10 @@ The following BNF defines the syntax =As
 
 To control the selection and installation of bundles, the following parameters may be used:
 
-* *version* - The version of the bundle to install. This is a version range specification
as per chapter 3.2.5 Version Ranges of the OSGi core specification. When this parameter is
declared as a single version - eg. *1.2.3* - it is interpreted as the version range *~[1.2.3,
∞~)*. The default value is *~[0.0.0,∞~)* to install the most recent version
of the bundle available.
-* *startlevel* - The start level to set for the bundle. This may be any positive integer
value. Default value is undefined to use the current initial bundle start level of the framework.
-* *entry* - The path of the Assembly Bundle entry providing the data to be installed.
-* *linked* - Defines whether the bundle should be started and stopped together with the Assembly
to which the bundle belongs. Default value is `true`.
+* **version** - The version of the bundle to install. This is a version range specification
as per chapter 3.2.5 Version Ranges of the OSGi core specification. When this parameter is
declared as a single version - eg. *1.2.3* - it is interpreted as the version range *~[1.2.3,
∞~)*. The default value is *~[0.0.0,∞~)* to install the most recent version
of the bundle available.
+* **startlevel** - The start level to set for the bundle. This may be any positive integer
value. Default value is undefined to use the current initial bundle start level of the framework.
+* **entry** - The path of the Assembly Bundle entry providing the data to be installed.
+* **linked** - Defines whether the bundle should be started and stopped together with the
Assembly to which the bundle belongs. Default value is `true`.
 
 If resolving the bundles results in more bundles to be downloaded from the bundle repository
to resolve the dependency, these bundles are always automatically started and assigned a startlevel
which is smaller than the smallest startlevel of any of the bundles listed.
 
@@ -97,14 +94,14 @@ If a bundle is defined in the `Assembly-
 
 Restrictions when packaging bundles with the Assembly:
 
-* *Dependency Resolution* - Any missing dependencies of the bundles to be installed will
not be resolved. That is, if the bundles fail to resolve, the Assembly fails to install.
-* *`version` Parameter* - The `version` parameter of the bundle installation declaration
is ignored because any JAR file whose name matches the bundle symbolic name to be installed,
is installed.
+* **Dependency Resolution** - Any missing dependencies of the bundles to be installed will
not be resolved. That is, if the bundles fail to resolve, the Assembly fails to install.
+* **`version` Parameter** - The `version` parameter of the bundle installation declaration
is ignored because any JAR file whose name matches the bundle symbolic name to be installed,
is installed.
 
 If the `Assembly-BundleRepository` header contains a comma-separated list of URL to OSGi
Bundle Repository descriptors and the OSGi Bundle Repository Service is available in the framework,
the bundles declared in the `Assembly-Bundles` header are resolved through the OSGi Bundle
Repository Service using the URL from the `Assembly-BundleRepository` header.
 
 If the bundles declare any dependencies, which may not be resolved by bundles already installed
in the framework or by any of the bundles to be installed, the OSGi Bundle Repository is used
to try to resolve these missing dependencies. If this resolution succeeds, installation of
the Assembly succeeds. Any bundles not declared in the Assembly but installed due to this
dependency resolution will not be assumed to belong to the Assembly. Hence, these bundles
will not be uninstalled (or updated) if the Assembly is uninstalled (or updated).
 
-* *Example* - Assume the `Assembly-Bundles` header is set to `org.apache.sling.sample1;entry=path.jar,org.apache.sling.sample2`.
The bundle `org.apache.sling.sample1` is then installed from the Assembly Bundle entry `path.jar`,
while the bundle `org.apache.sling.sample2` is resolved in the OSGi Bundle Repository.
+* **Example** - Assume the `Assembly-Bundles` header is set to `org.apache.sling.sample1;entry=path.jar,org.apache.sling.sample2`.
The bundle `org.apache.sling.sample1` is then installed from the Assembly Bundle entry `path.jar`,
while the bundle `org.apache.sling.sample2` is resolved in the OSGi Bundle Repository.
 
 
 

Modified: sling/site/trunk/content/site/.htaccess
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/site/.htaccess?rev=1529997&r1=1529996&r2=1529997&view=diff
==============================================================================
--- sling/site/trunk/content/site/.htaccess (original)
+++ sling/site/trunk/content/site/.htaccess Mon Oct  7 16:57:51 2013
@@ -60,3 +60,4 @@ Redirect Permanent /site/manipulating-co
 Redirect Permanent /site/logging.html /documentation/development/logging.html
 Redirect Permanent /site/bundle-resources-extensionsbundleresource.html /documentation/bundles/bundle-resources-extensions-bundleresource.html
 Redirect Permanent /site/client-request-logging.html /documentation/development/client-request-logging.html
+Redirect Permanent /site/assembly.html /old-stuff/assembly.html
\ No newline at end of file



Mime
View raw message