[jboss-cvs] JBossAS SVN: r63477 - in projects/microcontainer/trunk/docs/gettingstarted/src/docbkx/en: modules and 1 other directory.

[jboss-cvs-commits at lists.jboss.org]

Author: alesj
Date: 2007-06-12 10:50:37 -0400 (Tue, 12 Jun 2007)
New Revision: 63477

Added:
   projects/microcontainer/trunk/docs/gettingstarted/src/docbkx/en/modules/mbeans.xml
Modified:
   projects/microcontainer/trunk/docs/gettingstarted/src/docbkx/en/master.xml
   projects/microcontainer/trunk/docs/gettingstarted/src/docbkx/en/modules/modules.odg
   projects/microcontainer/trunk/docs/gettingstarted/src/docbkx/en/modules/osgi.xml
Log:
OSGi module, MBeans extensions.

Modified: projects/microcontainer/trunk/docs/gettingstarted/src/docbkx/en/master.xml
===================================================================
--- projects/microcontainer/trunk/docs/gettingstarted/src/docbkx/en/master.xml	2007-06-12 14:43:55 UTC (rev 63476)
+++ projects/microcontainer/trunk/docs/gettingstarted/src/docbkx/en/master.xml	2007-06-12 14:50:37 UTC (rev 63477)
@@ -59,6 +59,9 @@
    <xi:include href="modules/modules.xml"
                xml:base="./"
                xmlns:xi="http://www.w3.org/2001/XInclude"/>
+   <xi:include href="modules/mbeans.xml"
+               xml:base="./"
+               xmlns:xi="http://www.w3.org/2001/XInclude"/>
    <xi:include href="modules/classloader.xml"
                xml:base="./"
                xmlns:xi="http://www.w3.org/2001/XInclude"/>

Added: projects/microcontainer/trunk/docs/gettingstarted/src/docbkx/en/modules/mbeans.xml
===================================================================
--- projects/microcontainer/trunk/docs/gettingstarted/src/docbkx/en/modules/mbeans.xml	                        (rev 0)
+++ projects/microcontainer/trunk/docs/gettingstarted/src/docbkx/en/modules/mbeans.xml	2007-06-12 14:50:37 UTC (rev 63477)
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+      "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
+
+<chapter id="mbeans">
+   <title>MBeans extensions</title>
+
+   <para>
+      MBeans extensions ...
+   </para>
+</chapter>

Modified: projects/microcontainer/trunk/docs/gettingstarted/src/docbkx/en/modules/modules.odg
===================================================================
(Binary files differ)

Modified: projects/microcontainer/trunk/docs/gettingstarted/src/docbkx/en/modules/osgi.xml
===================================================================
--- projects/microcontainer/trunk/docs/gettingstarted/src/docbkx/en/modules/osgi.xml	2007-06-12 14:43:55 UTC (rev 63476)
+++ projects/microcontainer/trunk/docs/gettingstarted/src/docbkx/en/modules/osgi.xml	2007-06-12 14:50:37 UTC (rev 63477)
@@ -5,7 +5,40 @@
 <chapter id="osgi">
    <title>OSGi module</title>
 
+   <para>We can see an increased demand for <ulink url="http://www.osgi.org">OSGi</ulink> technology these days.
+      Developers and users specially like OSGi kind of Classloader wiring. Being able to have Class dependency defined
+      as a versioned package dependency is something we've been lacking for while now. There are new JSRs in the making,
+      that will eventually solve this problem, but OSGi is here and now.
+   </para>
+
+   <para>Looking at the OSGi framework we saw a lot similarity with what we already have with Microcontainer. Another
+      aspect of OSGi that is cruical part of the core Framework is Service Registry. A simple lookup pattern that
+      takes Classloading wiring into the consideration when doing Service lookup. While we already have contextual
+      awareness in Microcontainer implementing this was a matter of simple <varname>OSGi Facade</varname> over the
+      existing Microcontainer registry. Together with new <xref linkend="classloader"/> there is a fully
+      OSGi r4.1 compatible solution available with the 2.0.0 Microcontainer.
+   </para>
+
+   <para>OSGi usage in Microcontainer falls down to three different aspects:
+      <itemizedlist>
+         <listitem>new OSGi Classloader</listitem>
+         <listitem>declarative or programmatic OSGi services deployment</listitem>
+         <listitem>OBR (OSGi Bundle Repository) usage</listitem>
+      </itemizedlist>
+   </para>
+
    <para>
-      OSGi ...
+      The new OSGi Classloader is used as a default Classloader, it is backward compatible with the existing UCL.
    </para>
+
+   <para>
+      For the existing OSGi declarative services or programmatic usage via BundleActivator, there is a full support
+      of the OSGi core API. But for new service declaration, we encourage people to use much richer Microcontainer
+      IoC features. The Classloading behavior and Service Registry will take new Microcontainer services into
+      consideration.
+   </para>
+
+   <para>
+      OBR usage ...
+   </para>
 </chapter>