[jboss-cvs] JBossAS SVN: r91550 - in projects/jboss-osgi: projects/spi/trunk/src/main/java/org/jboss/osgi/spi/util and 6 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Jul 22 09:10:42 EDT 2009
Author: thomas.diesler at jboss.com
Date: 2009-07-22 09:10:41 -0400 (Wed, 22 Jul 2009)
New Revision: 91550
Added:
projects/jboss-osgi/projects/spi/trunk/src/main/java/org/jboss/osgi/spi/util/package.html
Modified:
projects/jboss-osgi/projects/runtime/deployers/trunk/src/main/java/org/jboss/osgi/deployer/BundleStartLevelDeployer.java
projects/jboss-osgi/trunk/distribution/docbook/en/images/izpack-done.png
projects/jboss-osgi/trunk/distribution/docbook/en/images/izpack-installpath.png
projects/jboss-osgi/trunk/distribution/docbook/en/images/izpack-structure.png
projects/jboss-osgi/trunk/distribution/docbook/en/images/izpack-verify.png
projects/jboss-osgi/trunk/distribution/docbook/en/images/izpack-welcome.png
projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch020-getting-started.xml
projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch030-runtime.xml
projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch050-developer-guide.xml
projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch060-husky-testing.xml
projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch070-provided-bundles.xml
projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch080-provided-examples.xml
projects/jboss-osgi/trunk/distribution/docbook/src/main/resources/bookinfo.xml
projects/jboss-osgi/trunk/distribution/installer/src/main/resources/installer/install-definition.xml
projects/jboss-osgi/trunk/pom.xml
projects/jboss-osgi/trunk/testsuite/example/src/test/java/org/jboss/test/osgi/example/blueprint/BlueprintTestCase.java
Log:
Update userguide
Modified: projects/jboss-osgi/projects/runtime/deployers/trunk/src/main/java/org/jboss/osgi/deployer/BundleStartLevelDeployer.java
===================================================================
--- projects/jboss-osgi/projects/runtime/deployers/trunk/src/main/java/org/jboss/osgi/deployer/BundleStartLevelDeployer.java 2009-07-22 12:51:01 UTC (rev 91549)
+++ projects/jboss-osgi/projects/runtime/deployers/trunk/src/main/java/org/jboss/osgi/deployer/BundleStartLevelDeployer.java 2009-07-22 13:10:41 UTC (rev 91550)
@@ -33,7 +33,11 @@
import org.osgi.util.tracker.ServiceTracker;
/**
- * This is the Bundle start level Deployer
+ * Sets the bundle's start level on the StartLevel service.
+ *
+ * A start level can be given when the bundle is deployed through the
+ * WebConsole. Currently, neither hot deployment nor SPI test framework
+ * deployments support start levels.
*
* @author Thomas.Diesler at jboss.com
* @since 08-Jul-2009
Added: projects/jboss-osgi/projects/spi/trunk/src/main/java/org/jboss/osgi/spi/util/package.html
===================================================================
--- projects/jboss-osgi/projects/spi/trunk/src/main/java/org/jboss/osgi/spi/util/package.html (rev 0)
+++ projects/jboss-osgi/projects/spi/trunk/src/main/java/org/jboss/osgi/spi/util/package.html 2009-07-22 13:10:41 UTC (rev 91550)
@@ -0,0 +1,5 @@
+<html>
+<body>
+A collection of SPI provided utilities.
+</body>
+</html>
Modified: projects/jboss-osgi/trunk/distribution/docbook/en/images/izpack-done.png
===================================================================
(Binary files differ)
Modified: projects/jboss-osgi/trunk/distribution/docbook/en/images/izpack-installpath.png
===================================================================
(Binary files differ)
Modified: projects/jboss-osgi/trunk/distribution/docbook/en/images/izpack-structure.png
===================================================================
(Binary files differ)
Modified: projects/jboss-osgi/trunk/distribution/docbook/en/images/izpack-verify.png
===================================================================
(Binary files differ)
Modified: projects/jboss-osgi/trunk/distribution/docbook/en/images/izpack-welcome.png
===================================================================
(Binary files differ)
Modified: projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch020-getting-started.xml
===================================================================
--- projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch020-getting-started.xml 2009-07-22 12:51:01 UTC (rev 91549)
+++ projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch020-getting-started.xml 2009-07-22 13:10:41 UTC (rev 91550)
@@ -21,7 +21,7 @@
<para>To run the installer execute the following command:</para>
<programlisting>
- java -jar jboss-osgi-installer-1.0.0.Beta2.jar
+ java -jar jboss-osgi-installer-1.0.0.Beta3.jar
</programlisting>
<para>The installer first shows a welcome screen</para>
@@ -127,7 +127,7 @@
JBoss OSGi Bootstrap Environment
- OSGI_HOME: /home/tdiesler/jboss-osgi-1.0.0.Beta2/runtime
+ OSGI_HOME: /home/tdiesler/jboss-osgi-1.0.0.Beta3/runtime
JAVA: /usr/java/jdk1.6/bin/java
@@ -135,7 +135,7 @@
=========================================================================
- 16:18:32,974 INFO [FelixIntegration] OSGi Integration Felix - 1.0.0.Beta2
+ 16:18:32,974 INFO [FelixIntegration] OSGi Integration Felix - 1.0.0.Beta3
16:18:33,403 INFO [FelixIntegration] Installed bundle [1]: org.osgi.compendium
16:18:33,412 INFO [FelixIntegration] Installed bundle [2]: org.apache.felix.log
16:18:33,425 INFO [FelixIntegration] Installed bundle [3]: jboss-osgi-common
@@ -161,13 +161,17 @@
deployment is verified by an accompaning test case</para>
<itemizedlist>
- <listitem><emphasis role="bold">LogServiceTestCase</emphasis> - Interact with a local and remote Log Service</listitem>
+ <listitem><emphasis role="bold">BlueprintTestCase</emphasis> - A simple Blueprint Container test</listitem>
+ <listitem><emphasis role="bold">DOMParserTestCase</emphasis> - A test that uses a DOM parser to read an XML document</listitem>
<listitem><emphasis role="bold">HttpServiceTestCase</emphasis> - Register servlets and resources with the HTTP Service</listitem>
+ <listitem><emphasis role="bold">JAXBTestCase</emphasis> - A test that uses JAXB to read an XML document</listitem>
<listitem><emphasis role="bold">JMXTestCase</emphasis> - Register an MBean through the JMX Service</listitem>
<listitem><emphasis role="bold">JNDITestCase</emphasis> - Bind objects to the Naming Service</listitem>
+ <listitem><emphasis role="bold">LogServiceTestCase</emphasis> - Interact with a local and remote Log Service</listitem>
<listitem><emphasis role="bold">MicrocontainerTestCase</emphasis> - Call a service from an MC bean and vica versa</listitem>
+ <listitem><emphasis role="bold">SAXParserTestCase</emphasis> - A test that uses a SAX parser to read an XML document</listitem>
+ <listitem><emphasis role="bold">SimpleHuskyTestCase</emphasis> - Accesses a service from within the test case</listitem>
<listitem><emphasis role="bold">SimpleTestCase</emphasis> - A simple bundle lifecycle test</listitem>
- <listitem><emphasis role="bold">SimpleHuskyTestCase</emphasis> - Accesses a service from within the test case</listitem>
</itemizedlist>
</sect1>
@@ -206,9 +210,7 @@
</imageobject>
</mediaobject>
- <note>
- <title>TODO: Cleanup and document console provided functionality</title>
- </note>
+ <para>The Web Console can also be used to install, start, stop and uninstall bundles.</para>
</sect1>
<sect1 xml:id="SecHudson">
@@ -288,7 +290,7 @@
Buildfile: build.xml
init:
- [echo] V1.0.0.Beta2
+ [echo] V1.0.0.Beta3
init-hudson:
[echo]
@@ -316,7 +318,7 @@
Buildfile: build.xml
init:
- [echo] V1.0.0.Beta2
+ [echo] V1.0.0.Beta3
init-hudson:
[echo]
@@ -342,7 +344,7 @@
Buildfile: build.xml
init:
- [echo] V1.0.0.Beta2
+ [echo] V1.0.0.Beta3
init-hudson:
[echo]
Modified: projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch030-runtime.xml
===================================================================
--- projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch030-runtime.xml 2009-07-22 12:51:01 UTC (rev 91549)
+++ projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch030-runtime.xml 2009-07-22 13:10:41 UTC (rev 91550)
@@ -9,8 +9,8 @@
<title>Overview</title>
- <para>Formerly a trimmed down <ulink url="http://http://jboss.org/jbossas">JBossAS</ulink> distribution, the
- JBoss OSGi Runtime has now evolved into a pure OSGi container onto which components, services and applications can be deployed.</para>
+ <para>The JBoss OSGi Runtime is an OSGi container onto which components,
+ services and applications can be deployed.</para>
<mediaobject>
<imageobject>
@@ -32,7 +32,7 @@
<para>Integration of the <ulink url="http://www.jboss.org/jbossmc">JBoss Microcontainer</ulink> as an OSGi service allows you
to write your applications in a POJO programming model without much "pollution" of OSGi specific API - the MC will do the
- wiring for you. Future releases of JBoss OSGi will come with a full implementation of
+ wiring for you. JBoss OSGi now also comes with an early alpha implementation of
<ulink url="http://jbossosgi.blogspot.com/2009/04/osgi-blueprint-service-rfc-124.html">Blueprint Service (RFC-124)</ulink>,
which standardizes this idea and takes it further.</para>
@@ -112,6 +112,12 @@
- so instead of simply installing a bundle to the underlying OSGi framework it passes to the chain of deployers which each deal with a specific
aspect of bundle deployment.
</listitem>
+
+ <listitem><emphasis role="bold">Blueprint Container Support</emphasis> -
+ The <ulink url="http://jbossosgi.blogspot.com/2009/04/osgi-blueprint-service-rfc-124.html">Blueprint Container</ulink> service allows bundles
+ to contain standard blueprint descriptors, which can be used for component wiring and injection of blueprint components.
+ The idea is to use a plain POJO programming model and let Blueprint do the wiring for you. There should be
+ no need for OSGi API to "pollute" your application logic.</listitem>
</itemizedlist>
</sect1>
@@ -122,10 +128,6 @@
contains the list of bundles that are installed/started automatically. You can start create you own profile
by setting up a new directory with your specific set of bundles.</para>
- <note>
- <title>TODO: [JBOSGI-98] Support configuration per profile</title>
- </note>
-
<para>A runtime profile can be started using the <emphasis role="bold">-c comand line option</emphasis>.</para>
<programlisting>
@@ -134,7 +136,7 @@
JBossOSGi Bootstrap Environment
- OSGI_HOME: /home/tdiesler/jboss-osgi-1.0.0.Beta2/runtime
+ OSGI_HOME: /home/tdiesler/jboss-osgi-1.0.0.Beta3/runtime
JAVA: /usr/java/jdk1.6/bin/java
@@ -142,7 +144,7 @@
=========================================================================
- 10:33:13,758 INFO [FelixIntegration] OSGi Integration Felix - 1.0.0.Beta2
+ 10:33:13,758 INFO [FelixIntegration] OSGi Integration Felix - 1.0.0.Beta3
10:33:14,185 INFO [FelixIntegration] Installed bundle [1]: org.osgi.compendium
10:33:14,194 INFO [FelixIntegration] Installed bundle [2]: org.apache.felix.log
10:33:14,203 INFO [FelixIntegration] Installed bundle [3]: jboss-osgi-common
@@ -202,6 +204,7 @@
<listitem><emphasis role="bold">jboss-osgi-jaxb.jar</emphasis> - JAXB support</listitem>
<listitem><emphasis role="bold">jboss-osgi-xml-binding.jar</emphasis> - XML Binding (JBossXB) support</listitem>
<listitem><emphasis role="bold">jboss-osgi-microcontainer.jar</emphasis> - Microcontainer support</listitem>
+ <listitem><emphasis role="bold">jboss-osgi-blueprint.jar</emphasis> - Blueprint Container support</listitem>
</itemizedlist>
</sect1>
Modified: projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch050-developer-guide.xml
===================================================================
--- projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch050-developer-guide.xml 2009-07-22 12:51:01 UTC (rev 91549)
+++ projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch050-developer-guide.xml 2009-07-22 13:10:41 UTC (rev 91550)
@@ -24,17 +24,17 @@
</imageobject>
</mediaobject>
- <para>The latest version of the <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-spi/apidocs">JBoss OSGi SPI</ulink>
- JavaDoc is published online as part of the JBoss OSGi <ulink url="http://jbmuc.dyndns.org:8280/hudson">Hudson QA Environment</ulink>.</para>
+ <para>The latest version of the <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-spi/apidocs">JBoss OSGi SPI</ulink>.</para>
<itemizedlist>
- <listitem><ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/package-summary.html">org.jboss.osgi.spi</ulink> - Common classes and interfaces.</listitem>
- <listitem><ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/capability/package-summary.html">org.jboss.osgi.spi.capability</ulink> - Capabilities that can be installed in the OSGi framework.</listitem>
- <listitem><ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/framework/package-summary.html">org.jboss.osgi.spi.framework</ulink> - Framework integration and bootstrap.</listitem>
- <listitem><ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/logging/package-summary.html">org.jboss.osgi.spi.logging</ulink> - Support for Bundle logging.</listitem>
- <listitem><ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/management/package-summary.html">org.jboss.osgi.spi.management</ulink> - Management view on deployed bundles.</listitem>
- <listitem><ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/service/package-summary.html">org.jboss.osgi.spi.service</ulink> - A collection of SPI provided services.</listitem>
- <listitem><ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/testing/package-summary.html">org.jboss.osgi.spi.testing</ulink> - OSGi test support classes and interfaces.</listitem>
+ <listitem><ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/package-summary.html">org.jboss.osgi.spi</ulink> - Common classes and interfaces.</listitem>
+ <listitem><ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/capability/package-summary.html">org.jboss.osgi.spi.capability</ulink> - Capabilities that can be installed in the OSGi framework.</listitem>
+ <listitem><ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/framework/package-summary.html">org.jboss.osgi.spi.framework</ulink> - Framework integration and bootstrap.</listitem>
+ <listitem><ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/logging/package-summary.html">org.jboss.osgi.spi.logging</ulink> - Support for Bundle logging.</listitem>
+ <listitem><ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/management/package-summary.html">org.jboss.osgi.spi.management</ulink> - Management view on deployed bundles.</listitem>
+ <listitem><ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/service/package-summary.html">org.jboss.osgi.spi.service</ulink> - A collection of SPI provided services.</listitem>
+ <listitem><ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/testing/package-summary.html">org.jboss.osgi.spi.testing</ulink> - OSGi test support classes and interfaces.</listitem>
+ <listitem><ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/util/package-summary.html">org.jboss.osgi.spi.util</ulink> - A collection of SPI provided utilities.</listitem>
</itemizedlist>
<emphasis role="bold">Bootstrapping JBoss OSGi</emphasis>
@@ -72,8 +72,8 @@
<para>The JBoss OSGi SPI comes with two bootstrap providers:</para>
<itemizedlist>
- <listitem><ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/framework/PropertiesBootstrapProvider.html">PropertiesBootstrapProvider</ulink></listitem>
- <listitem><ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/framework/MicrocontainerBootstrapProvider.html">MicrocontainerBootstrapProvider</ulink></listitem>
+ <listitem><ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/framework/PropertiesBootstrapProvider.html">PropertiesBootstrapProvider</ulink></listitem>
+ <listitem><ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/framework/MicrocontainerBootstrapProvider.html">MicrocontainerBootstrapProvider</ulink></listitem>
</itemizedlist>
<para>OSGiBootstrapProvider implementations that read their configurtation from some other source are possible, but currently not
@@ -99,6 +99,7 @@
<listitem><emphasis role="bold">BundleManagementDeployer</emphasis> - Register the Bundle as MBean with JMX</listitem>
<listitem><emphasis role="bold">BundleMetaDataDeployer</emphasis> - Create BundleMetaData from Manifest Headers</listitem>
<listitem><emphasis role="bold">BundleRealDeployer</emphasis> - Installs the Bundle into the Framework's SystemContext</listitem>
+ <listitem><emphasis role="bold">BundleStartLevelDeployer</emphasis> - Sets the bundle's start level on the StartLevel service</listitem>
<listitem><emphasis role="bold">BundleStartStopDeployer</emphasis> - Starts the Bundle when dependencies are resolved</listitem>
<listitem><emphasis role="bold">BundleStructureDeployer</emphasis> - Determine the structure of a Bundle deployment</listitem>
</itemizedlist>
@@ -131,6 +132,12 @@
<para>On undeploy the Bundle gets uninstalled from the Framework's SystemContext.</para>
+ <emphasis role="bold">BundleStartLevelDeployer</emphasis>
+
+ <para>Sets the bundle's start level on the StartLevel service. A start level can be given when
+ the bundle is deployed through the WebConsole. Currently, neither hot deployment nor SPI test
+ framework deployments support start levels.</para>
+
<emphasis role="bold">BundleStartStopDeployer</emphasis>
<para>The BundleStartStopDeployer currently works in two modes:</para>
@@ -174,7 +181,7 @@
<emphasis role="bold">The ManagedFramework</emphasis>
- <para>The <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/management/ManagedFrameworkMBean.html">
+ <para>The <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/management/ManagedFrameworkMBean.html">
ManagedFramework</ulink> gives you access to the MBean views of the deployed Bundles. It is registerd under the name:</para>
<itemizedlist>
@@ -183,7 +190,7 @@
<emphasis role="bold">The ManagedBundle</emphasis>
- <para>The <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/management/ManagedBundle.html">
+ <para>The <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/management/ManagedBundle.html">
ManagedBundle</ulink> gives you access to the MBean views of a deployed Bundle. It is registerd under the name:</para>
<itemizedlist>
@@ -193,7 +200,7 @@
<emphasis role="bold">Accessing the Management Objects</emphasis>
<para>If you work with the JBoss OSGi Testsuite you get access to the Managed Objects through the JBoss OSGi SPI provided
- <ulink url="http://junit.sourceforge.net/">JUnit</ulink> support package <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/testing/package-summary.html">org.jboss.osgi.spi.testing</ulink>.
+ <ulink url="http://junit.sourceforge.net/">JUnit</ulink> support package <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/testing/package-summary.html">org.jboss.osgi.spi.testing</ulink>.
</para>
<para>If you install JBoss OSGi in an already existing JBossAS instance you also get access to the Managed Objects through the JBoss provided
@@ -214,7 +221,7 @@
<title>Writing Test Cases</title>
<para>JBoss OSGi comes with <ulink url="http://www.junit.org">JUnit</ulink> test support as part of the SPI provided
- <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/testing/package-summary.html">org.jboss.osgi.spi.testing</ulink>
+ <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/testing/package-summary.html">org.jboss.osgi.spi.testing</ulink>
package. There are two distinct test scenarios that we support:</para>
<itemizedlist>
Modified: projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch060-husky-testing.xml
===================================================================
--- projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch060-husky-testing.xml 2009-07-22 12:51:01 UTC (rev 91549)
+++ projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch060-husky-testing.xml 2009-07-22 13:10:41 UTC (rev 91550)
@@ -64,39 +64,39 @@
<para>Here is how it works </para>
<orderedlist>
- <listitem>A <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/Bridge.html">Bridge</ulink>
+ <listitem>A <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/Bridge.html">Bridge</ulink>
intercepts a test and determines the FQN of the test case and the test method from the call stack. It then delegates the execution to the same
(or another) test in and isolated test environment. An isolated test environment is one that does not have the same class loading space as
the test itself.</listitem>
- <listitem>A Bridge is associated with an <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/Invoker.html">
+ <listitem>A Bridge is associated with an <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/Invoker.html">
Invoker</ulink>. Invokers may be arbitarily complex. Local 'in proccess' invokers are possible just as well as remote invokers. </listitem>
- <listitem>The Invoker sends the <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/Request.html">
- Request</ulink> to a <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/runtime/Connector.html">
+ <listitem>The Invoker sends the <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/Request.html">
+ Request</ulink> to a <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/runtime/Connector.html">
Connector</ulink> in the isolated test environment.</listitem>
- <listitem>A Connector has associated <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/runtime/PackageListener.html">
+ <listitem>A Connector has associated <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/runtime/PackageListener.html">
PackageListeners</ulink> that are responsible for processing test cases for their respective test packages.</listitem>
- <listitem>A PackageListeners delegates the Request to a test <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/runtime/Runner.html">
- Runner</ulink>, typicaly this would be a <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/runtime/junit/JUnitRunner.html">
+ <listitem>A PackageListeners delegates the Request to a test <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/runtime/Runner.html">
+ Runner</ulink>, typicaly this would be a <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/runtime/junit/JUnitRunner.html">
JUnitRunner</ulink>.</listitem>
- <listitem>The Runner injects the <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/Context.html">
- Context</ulink> into the test case and returns a <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/Response.html">
+ <listitem>The Runner injects the <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/Context.html">
+ Context</ulink> into the test case and returns a <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/Response.html">
Response</ulink>, which the Connector returns to the Invoker.</listitem>
- <listitem>The Bridge finally translates potential <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/Failure.html">
+ <listitem>The Bridge finally translates potential <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/Failure.html">
Failures</ulink> that may be contained in the Result, to test failures on the client side.</listitem>
</orderedlist>
<para>The JBoss OSGi <emphasis role="bold">jboss-osgi-husky.jar</emphasis> bundle registers the Connectors.
- The <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/runtime/osgi/JMXConnector.html">
+ The <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/runtime/osgi/JMXConnector.html">
JMXConnector</ulink> is always registered.
- The <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/runtime/osgi/SocketConnector.html">
+ The <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/runtime/osgi/SocketConnector.html">
SocketConnector</ulink> is registered when the appropriate configuration options are set. It then registers the
- <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/runtime/osgi/HuskyExtender.html">HuskyExtender</ulink>,
+ <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-husky-parent/jboss-osgi-husky/apidocs/org/jboss/osgi/husky/runtime/osgi/HuskyExtender.html">HuskyExtender</ulink>,
which is a <ulink url="http://www.osgi.org/javadoc/r4v41/org/osgi/framework/BundleListener.html">BundleListener</ulink> that inspects every
incomming bundle for the <emphasis role="bold">Test-Package</emphasis> manifest header. The Extender creates a PackageListener
for every package in the 'Test-Package' manifest header and registers them with the available Connectors.</para>
Modified: projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch070-provided-bundles.xml
===================================================================
--- projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch070-provided-bundles.xml 2009-07-22 12:51:01 UTC (rev 91549)
+++ projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch070-provided-bundles.xml 2009-07-22 13:10:41 UTC (rev 91550)
@@ -5,10 +5,43 @@
<title>Provided Bundles and Services</title>
+ <sect1 xml:id="SecBundleXerces">
+ <title>XML Parser Services</title>
+
+ <para>The JBoss OSGi <emphasis role="bold">jboss-osgi-apache-xerces.jar</emphasis> bundle provides services
+ from DOM and SAX parsing.</para>
+
+ <para>The services are registered with the Framework under the name</para>
+
+ <itemizedlist>
+ <listitem><emphasis role="bold">javax.xml.parsers.SAXParserFactory</emphasis></listitem>
+ <listitem><emphasis role="bold">javax.xml.parsers.DocumentBuilderFactory</emphasis></listitem>
+ </itemizedlist>
+
+ <para>Please see <ulink url="http://www.osgi.org/javadoc/r4v41/org/osgi/util/xml/XMLParserActivator.html">XMLParserActivator</ulink>
+ for details.</para>
+
+ </sect1>
+
+ <sect1 xml:id="SecBundleJAXB">
+ <title>JAXB Service</title>
+
+ <para>The JBoss OSGi <emphasis role="bold">jboss-osgi-jaxb.jar</emphasis> bundle provides a service
+ to create <ulink url="http://java.sun.com/javase/6/docs/api/javax/xml/bind/JAXBContext.html">JAXBContext</ulink>
+ instances.</para>
+
+ <para>The service is registered with the Framework under the name</para>
+
+ <itemizedlist>
+ <listitem><emphasis role="bold">org.jboss.osgi.jaxb.JAXBService</emphasis></listitem>
+ </itemizedlist>
+
+ </sect1>
+
<sect1 xml:id="SecBundleJMX">
<title>JMX Service</title>
- <para>The JBoss OSGi <emphasis role="bold">jboss-osgi-jmx.jar</emphasis> bundle activator discoveres and registers the
+ <para>The JBoss OSGi <emphasis role="bold">jboss-osgi-jmx.jar</emphasis> bundle activator discovers and registers the
<ulink url="http://java.sun.com/javase/6/docs/api/javax/management/MBeanServer.html">MBeanServer</ulink> with the framework.
It also tracks the naming service and binds the RMIAdaptor into JNDI for remote JMX access</para>
@@ -135,7 +168,7 @@
<para>On the client side you can install an arbitrary <ulink url="http://www.osgi.org/javadoc/r4v41/org/osgi/service/log/LogListener.html">LogListener</ulink>
with the <ulink url="http://www.osgi.org/javadoc/r4v41/org/osgi/service/log/LogReaderService.html">RemoteLogReaderService</ulink>. The testsuite typically
- installs an <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/logging/LogEntryCache.html">LogEntryCache</ulink>
+ installs an <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/logging/LogEntryCache.html">LogEntryCache</ulink>
that filters the received log messages.</para>
<programlisting role="JAVA">
@@ -160,11 +193,11 @@
<sect1 xml:id="SecBundleMicrocontainer">
<title>Microcontainer Service</title>
- <para>JBoss OSGi SPI comes with a service that give access to the <ulink url="http://www.jboss.org/jbossmc">JBoss Microcontainer</ulink> Kernel.
+ <para>The JBoss OSGi <emphasis role="bold">jboss-osgi-microcontainer.jar</emphasis> bundle provides a service that give access to the <ulink url="http://www.jboss.org/jbossmc">JBoss Microcontainer</ulink> Kernel.
The service is registered with the Framework under the name</para>
<itemizedlist>
- <listitem><emphasis role="bold">org.jboss.osgi.spi.service.MicrocontainerService</emphasis></listitem>
+ <listitem><emphasis role="bold">org.jboss.osgi.microcontainer.MicrocontainerService</emphasis></listitem>
</itemizedlist>
<para>Here is an example of how an OSGi component can access an arbitrary MC bean.</para>
@@ -183,4 +216,16 @@
</programlisting>
</sect1>
+ <sect1 xml:id="SecBundleBlueprint">
+ <title>Blueprint Container Service</title>
+
+ <para>The JBoss OSGi <emphasis role="bold">jboss-osgi-blueprint.jar</emphasis> bundle provides
+ a early access of a Blueprint extender service.</para>
+
+ <para>The <ulink url="http://jbossosgi.blogspot.com/2009/04/osgi-blueprint-service-rfc-124.html">Blueprint Container</ulink>
+ service allows bundles to contain standard blueprint descriptors, which can be used for component wiring
+ and injection of blueprint components. The idea is to use a plain POJO programming model and let
+ Blueprint do the wiring for you. There should be no need for OSGi API to "pollute" your application logic.</para>
+ </sect1>
+
</chapter>
Modified: projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch080-provided-examples.xml
===================================================================
--- projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch080-provided-examples.xml 2009-07-22 12:51:01 UTC (rev 91549)
+++ projects/jboss-osgi/trunk/distribution/docbook/en/modules/ch080-provided-examples.xml 2009-07-22 13:10:41 UTC (rev 91550)
@@ -126,7 +126,7 @@
<note>
<para>Please note that access to the MBeanServer from the test case is part of the
- <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/testing/OSGiRuntime.html">
+ <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/testing/OSGiRuntime.html">
OSGiRuntime</ulink> abstraction.</para>
</note>
@@ -172,7 +172,7 @@
<note>
<para>Please note that access to the InitialContext from the test case is part of the
- <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta2/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/testing/OSGiRuntime.html">
+ <ulink url="http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta3/jboss-osgi-spi/apidocs/org/jboss/osgi/spi/testing/OSGiRuntime.html">
OSGiRuntime</ulink> abstraction.</para>
</note>
Modified: projects/jboss-osgi/trunk/distribution/docbook/src/main/resources/bookinfo.xml
===================================================================
--- projects/jboss-osgi/trunk/distribution/docbook/src/main/resources/bookinfo.xml 2009-07-22 12:51:01 UTC (rev 91549)
+++ projects/jboss-osgi/trunk/distribution/docbook/src/main/resources/bookinfo.xml 2009-07-22 13:10:41 UTC (rev 91550)
@@ -4,12 +4,13 @@
<bookinfo>
<title>JBossOSGi - User Guide</title>
+
+ <releaseinfo>Version: 1.0.0.Beta3</releaseinfo>
+ <pubdate>Date: 22-Jul-2009</pubdate>
+
<!--
- <releaseinfo>Version: 1.0.0.Beta2</releaseinfo>
- <pubdate>Date: 03-Jun-2009 22:55:42</pubdate>
- -->
-
<releaseinfo>Version: ${version} (Draft)</releaseinfo>
<pubdate>Date: ${buildNumber}</pubdate>
+ -->
</bookinfo>
Modified: projects/jboss-osgi/trunk/distribution/installer/src/main/resources/installer/install-definition.xml
===================================================================
--- projects/jboss-osgi/trunk/distribution/installer/src/main/resources/installer/install-definition.xml 2009-07-22 12:51:01 UTC (rev 91549)
+++ projects/jboss-osgi/trunk/distribution/installer/src/main/resources/installer/install-definition.xml 2009-07-22 13:10:41 UTC (rev 91550)
@@ -115,6 +115,7 @@
<include name="jboss-logging-log4j-javadoc.jar" />
<include name="jboss-logging-spi-javadoc.jar" />
<include name="jboss-osgi-apache-xerces-javadoc.jar" />
+ <include name="jboss-osgi-blueprint-javadoc.jar" />
<include name="jboss-osgi-common-core-javadoc.jar" />
<include name="jboss-osgi-common-javadoc.jar" />
<include name="jboss-osgi-deployers-javadoc.jar" />
@@ -142,6 +143,7 @@
<include name="jboss-logging-log4j-sources.jar" />
<include name="jboss-logging-spi-sources.jar" />
<include name="jboss-osgi-apache-xerces-sources.jar" />
+ <include name="jboss-osgi-blueprint-sources.jar" />
<include name="jboss-osgi-common-core-sources.jar" />
<include name="jboss-osgi-common-sources.jar" />
<include name="jboss-osgi-deployers-sources.jar" />
@@ -239,6 +241,7 @@
<include name="org.apache.felix.metatype.jar" />
<!-- all -->
<include name="jboss-osgi-apache-xerces.jar" />
+ <include name="jboss-osgi-blueprint.jar" />
<include name="jboss-osgi-jaxb.jar" />
<include name="jboss-osgi-microcontainer.jar" />
<include name="jboss-osgi-xml-binding.jar" />
Modified: projects/jboss-osgi/trunk/pom.xml
===================================================================
--- projects/jboss-osgi/trunk/pom.xml 2009-07-22 12:51:01 UTC (rev 91549)
+++ projects/jboss-osgi/trunk/pom.xml 2009-07-22 13:10:41 UTC (rev 91550)
@@ -87,19 +87,6 @@
</repository>
</repositories>
- <!-- DistributionManagement -->
- <distributionManagement>
- <site>
- <id>jbmuc.dyndns.org</id>
- <url>scp://jbmuc.dyndns.org/var/www/html/jboss-osgi-${version}
- </url>
- </site>
- <!--
- To copy the userguide run:
- scp -r docbook/target/docbook/publish/en-US/* jbmuc.dyndns.org:/var/www/html/jboss-osgi-${version}/userguide/
- -->
- </distributionManagement>
-
<!-- Profiles -->
<profiles>
Modified: projects/jboss-osgi/trunk/testsuite/example/src/test/java/org/jboss/test/osgi/example/blueprint/BlueprintTestCase.java
===================================================================
--- projects/jboss-osgi/trunk/testsuite/example/src/test/java/org/jboss/test/osgi/example/blueprint/BlueprintTestCase.java 2009-07-22 12:51:01 UTC (rev 91549)
+++ projects/jboss-osgi/trunk/testsuite/example/src/test/java/org/jboss/test/osgi/example/blueprint/BlueprintTestCase.java 2009-07-22 13:10:41 UTC (rev 91550)
@@ -49,7 +49,7 @@
import org.osgi.service.blueprint.container.BlueprintContainer;
/**
- * Blueprint example test.
+ * A simple Blueprint Container test.
*
* @author thomas.diesler at jboss.com
* @since 12-Jul-2009
More information about the jboss-cvs-commits
mailing list