[jboss-cvs] JBossAS SVN: r86210 - in projects/jboss-osgi/trunk/build: docbook and 3 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Mar 23 11:12:01 EDT 2009
Author: thomas.diesler at jboss.com
Date: 2009-03-23 11:12:01 -0400 (Mon, 23 Mar 2009)
New Revision: 86210
Added:
projects/jboss-osgi/trunk/build/docbook/en/images/osgi-classloader.png
projects/jboss-osgi/trunk/build/docbook/en/images/osgi-config-service.png
projects/jboss-osgi/trunk/build/docbook/en/images/osgi-delegation.png
projects/jboss-osgi/trunk/build/docbook/en/images/osgi-layers.png
projects/jboss-osgi/trunk/build/docbook/en/images/osgi-life-cycle.png
projects/jboss-osgi/trunk/build/docbook/en/images/osgi-service-registration.png
projects/jboss-osgi/trunk/build/docbook/en/images/osgi-version-constraint.png
projects/jboss-osgi/trunk/build/docbook/en/modules/frameworkintegration.xml
projects/jboss-osgi/trunk/build/docbook/en/modules/providedservices.xml
Modified:
projects/jboss-osgi/trunk/build/distribution/pom.xml
projects/jboss-osgi/trunk/build/docbook/en/master.xml
projects/jboss-osgi/trunk/build/docbook/en/modules/gettingstarted.xml
projects/jboss-osgi/trunk/build/docbook/en/modules/introduction.xml
projects/jboss-osgi/trunk/build/docbook/pom.xml
Log:
Userguide - Intro
Modified: projects/jboss-osgi/trunk/build/distribution/pom.xml
===================================================================
--- projects/jboss-osgi/trunk/build/distribution/pom.xml 2009-03-23 15:11:04 UTC (rev 86209)
+++ projects/jboss-osgi/trunk/build/distribution/pom.xml 2009-03-23 15:12:01 UTC (rev 86210)
@@ -104,21 +104,21 @@
<dependency>
<groupId>org.jboss.osgi</groupId>
<artifactId>jboss-osgi-userguide</artifactId>
- <classifier>pdf</classifier>
+ <classifier>html</classifier>
<version>${version}</version>
<type>war</type>
</dependency>
<dependency>
<groupId>org.jboss.osgi</groupId>
<artifactId>jboss-osgi-userguide</artifactId>
- <classifier>html</classifier>
+ <classifier>html_single</classifier>
<version>${version}</version>
<type>war</type>
</dependency>
<dependency>
<groupId>org.jboss.osgi</groupId>
<artifactId>jboss-osgi-userguide</artifactId>
- <classifier>html_single</classifier>
+ <classifier>pdf</classifier>
<version>${version}</version>
<type>war</type>
</dependency>
Added: projects/jboss-osgi/trunk/build/docbook/en/images/osgi-classloader.png
===================================================================
(Binary files differ)
Property changes on: projects/jboss-osgi/trunk/build/docbook/en/images/osgi-classloader.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: projects/jboss-osgi/trunk/build/docbook/en/images/osgi-config-service.png
===================================================================
(Binary files differ)
Property changes on: projects/jboss-osgi/trunk/build/docbook/en/images/osgi-config-service.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: projects/jboss-osgi/trunk/build/docbook/en/images/osgi-delegation.png
===================================================================
(Binary files differ)
Property changes on: projects/jboss-osgi/trunk/build/docbook/en/images/osgi-delegation.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: projects/jboss-osgi/trunk/build/docbook/en/images/osgi-layers.png
===================================================================
(Binary files differ)
Property changes on: projects/jboss-osgi/trunk/build/docbook/en/images/osgi-layers.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: projects/jboss-osgi/trunk/build/docbook/en/images/osgi-life-cycle.png
===================================================================
(Binary files differ)
Property changes on: projects/jboss-osgi/trunk/build/docbook/en/images/osgi-life-cycle.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: projects/jboss-osgi/trunk/build/docbook/en/images/osgi-service-registration.png
===================================================================
(Binary files differ)
Property changes on: projects/jboss-osgi/trunk/build/docbook/en/images/osgi-service-registration.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: projects/jboss-osgi/trunk/build/docbook/en/images/osgi-version-constraint.png
===================================================================
(Binary files differ)
Property changes on: projects/jboss-osgi/trunk/build/docbook/en/images/osgi-version-constraint.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Modified: projects/jboss-osgi/trunk/build/docbook/en/master.xml
===================================================================
--- projects/jboss-osgi/trunk/build/docbook/en/master.xml 2009-03-23 15:11:04 UTC (rev 86209)
+++ projects/jboss-osgi/trunk/build/docbook/en/master.xml 2009-03-23 15:12:01 UTC (rev 86210)
@@ -2,8 +2,10 @@
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3CR3//EN"
"../dtd/docbookx.dtd" [
-<!ENTITY introduction SYSTEM "modules/introduction.xml">
-<!ENTITY gettingstarted SYSTEM "modules/gettingstarted.xml">
+<!ENTITY Chap_Introduction SYSTEM "modules/introduction.xml">
+<!ENTITY Chap_Getting_Started SYSTEM "modules/gettingstarted.xml">
+<!ENTITY Chap_Framework_Integration SYSTEM "modules/frameworkintegration.xml">
+<!ENTITY Chap_Provided_Services SYSTEM "modules/providedservices.xml">
<!ENTITY version "1.0.0.Alpha3">
]>
@@ -12,16 +14,13 @@
<title>JBossOSGi</title>
<subtitle>User Guide</subtitle>
<releaseinfo>&version;</releaseinfo>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/jbpm_logotype_jpdl.svg" align="center" />
- </imageobject>
- </mediaobject>
</bookinfo>
<toc />
- &introduction;
- &gettingstarted;
+ &Chap_Introduction;
+ &Chap_Getting_Started;
+ &Chap_Framework_Integration;
+ &Chap_Provided_Services;
</book>
\ No newline at end of file
Added: projects/jboss-osgi/trunk/build/docbook/en/modules/frameworkintegration.xml
===================================================================
--- projects/jboss-osgi/trunk/build/docbook/en/modules/frameworkintegration.xml (rev 0)
+++ projects/jboss-osgi/trunk/build/docbook/en/modules/frameworkintegration.xml 2009-03-23 15:12:01 UTC (rev 86210)
@@ -0,0 +1,20 @@
+<chapter id="Chap_Framework_Integration">
+
+ <title>Framework Integration</title>
+
+ <section id="Sec_Integration_Felix">
+ <title>Apache Felix Integration</title>
+ <para>TODO</para>
+ </section>
+
+ <section id="Sec_Integration_Equinox">
+ <title>Equinox Integration</title>
+ <para>TODO</para>
+ </section>
+
+ <section id="Sec_Integration_Knopflerfish">
+ <title>Knopflerfish Integration</title>
+ <para>TODO</para>
+ </section>
+
+</chapter>
Property changes on: projects/jboss-osgi/trunk/build/docbook/en/modules/frameworkintegration.xml
___________________________________________________________________
Name: svn:keywords
+ Id Revision
Name: svn:eol-style
+ LF
Modified: projects/jboss-osgi/trunk/build/docbook/en/modules/gettingstarted.xml
===================================================================
--- projects/jboss-osgi/trunk/build/docbook/en/modules/gettingstarted.xml 2009-03-23 15:11:04 UTC (rev 86209)
+++ projects/jboss-osgi/trunk/build/docbook/en/modules/gettingstarted.xml 2009-03-23 15:12:01 UTC (rev 86210)
@@ -1,16 +1,16 @@
-<chapter id="gettingstarted">
+<chapter id="Chap_Getting_Started">
<title>Getting Started</title>
<para>This chapter takes you through the first steps of getting JBossOSGi and
provides the initial pointers to get up and running in no time.</para>
- <section id="download_and_install">
- <title>Downloading and Installing JBossOSGi</title>
+ <section id="Sec_Download_Install">
+ <title>Installing JBossOSGi</title>
</section>
<section>
- <title>The JBossOSGi Wiki</title>
+ <title>Project Infrastructure</title>
<para>The <ulink url="http://www.jboss.org/community/docs/DOC-13273">JBossOSGi Wiki</ulink> provides
news, details about forums, mailing lists, issue tracker, downloads, source repositories, etc.
</para>
Modified: projects/jboss-osgi/trunk/build/docbook/en/modules/introduction.xml
===================================================================
--- projects/jboss-osgi/trunk/build/docbook/en/modules/introduction.xml 2009-03-23 15:11:04 UTC (rev 86209)
+++ projects/jboss-osgi/trunk/build/docbook/en/modules/introduction.xml 2009-03-23 15:12:01 UTC (rev 86210)
@@ -1,18 +1,349 @@
-<chapter id="introduction">
+<!--
+ $Id$
+-->
+<chapter id="ChapIntroduction">
<title>Introduction</title>
- <para>The <ulink url="http://www2.osgi.org/Release4/HomePage">Open Services Gateway Initiative (OSGi)</ulink>,
- specifications define a standardized, component-oriented, computing environment for networked services that is the foundation
- of an enhanced service-oriented architecture.</para>
+ <sect1>
+ <title>What is OSGi</title>
+
+ <para>The <ulink url="http://www2.osgi.org/Release4/HomePage">Open Services Gateway Initiative (OSGi)</ulink>,
+ specifications define a standardized, component-oriented, computing environment for networked services that is the foundation
+ of an enhanced service-oriented architecture.</para>
+
+ <para>The OSGi specification defines two things:</para>
+
+ <itemizedlist>
+ <listitem>A set of services that an OSGi container must implement</listitem>
+ <listitem>A contract between the container and your application</listitem>
+ </itemizedlist>
+
+ <para>Developing on the OSGi platform means first building your application using OSGi APIs, then deploying it in an OSGi container.</para>
+
+ <sect2>
+ <title>What does OSGi offer to Java developers?</title>
+
+ <para>OSGi modules provide classloader semantics to partially expose code that can then be consumed by other modules.
+ The implementation details of a module, although scoped public by the Java programming language, remain private to the module.
+ On top of that you can install multiple versions of the same code and resolve dependencies by version and other criteria.
+ OSGi also offers advanced security and lifecycle, which I'll explain in more detail further down.</para>
+ </sect2>
+
+ <sect2>
+ <title>What kind of applications benefit from OSGi?</title>
+
+ <para>Any application that is designed in a modular fashion where it is necessary to start, stop, update individual modules with minimal impact
+ on other modules. Modules can define their own transitive dependencies without the need to resolve these dependencies at the container level.
+ The OSGi platform builds an exellent foundation for the next generation JBoss ESB for example.</para>
+ </sect2>
+
+ <sect2>
+ <title>Should Java EE developers adopt the OSGi programming model?</title>
+
+ <para>Probably not. The OSGi runtime may be used internally by Java EE container providers to achieve the desired isolation and configuration
+ flexibility that the container whishes to provide. At the application programming level, the Java EE model will continue to exist in its own right,
+ wheras the OSGi model may provide the more suitable runtime environment for applications that require the modular isolation, security and lifecycle
+ management that OSGi offers.</para>
+ </sect2>
+ </sect1>
+
+ <sect1>
+ <title>OSGi Framework Overview</title>
+
+ <para>The functionality of the Framework is divided in the following layers:</para>
+
+ <itemizedlist>
+ <listitem>Security Layer</listitem>
+ <listitem>Module Layer</listitem>
+ <listitem>Life Cycle Layer</listitem>
+ <listitem>Service Layer</listitem>
+ <listitem>Actual Services</listitem>
+ </itemizedlist>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/osgi-layers.png"/>
+ </imageobject>
+ </mediaobject>
- <para>The OSGi specification defines two things:</para>
+ <sect2>
+ <title>OSGi Security Layer</title>
+
+ <para>The OSGi Security Layer is an optional layer that underlies the OSGi Service Platform.
+ The layer is based on the Java 2 security architecture. It provides the infrastructure to deploy and manage
+ applications that must run in fine grained controlled environments.</para>
+
+ <para>The OSGi Service Platform can authenticate code in the following ways:</para>
+
+ <itemizedlist>
+ <listitem>By location</listitem>
+ <listitem>By signer</listitem>
+ </itemizedlist>
+
+ <para>For example, an Operator can grant the ACME company the right to use networking on their devices.
+ The ACME company can then use networking in every bundle they digitally sign and deploy on the Operator’s device.
+ Also, a specific bundle can be granted permission to only manage the life cycle of bundles that are signed by the ACME company.</para>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/osgi-delegation.png"/>
+ </imageobject>
+ </mediaobject>
+ </sect2>
+
+ <sect2>
+ <title>OSGi Module Layer</title>
+
+ <para>The OSGi Module Layer provides a generic and standardized solution for Java modularization.
+ The Framework defines a unit of modularization, called a bundle. A bundle is comprised of Java classes and other resources,
+ which together can provide functions to end users. Bundles can share Java packages among an exporter bundle and an importer bundle
+ in a well-defined way.</para>
+
+ <para>Once a <emphasis role="bold">Bundle</emphasis> is started, its functionality is provided and services are exposed to other bundles installed in the OSGi Service Platform.
+ A bundle can carry descriptive information about itself in the manifest file that is contained in its JAR file.
+ Here are a few important <emphasis role="bold">Manifest Headers</emphasis> defined by the OSGi Framework:</para>
+
+ <itemizedlist>
+ <listitem><emphasis role="bold">Bundle-Activator</emphasis> - class used to start, stop the bundle</listitem>
+ <listitem><emphasis role="bold">Bundle-SymbolicName</emphasis> - identifies the bundle</listitem>
+ <listitem><emphasis role="bold">Bundle-Version</emphasis> - specifies the version of the bundle</listitem>
+ <listitem><emphasis role="bold">Export-Package</emphasis> - declaration of exported packages</listitem>
+ <listitem><emphasis role="bold">Import-Package</emphasis> - declaration of imported packages</listitem>
+ </itemizedlist>
+
+ <para>The notion of OSGi Version Range describes a range of versions using a mathematical interval notation. For example</para>
+
+ <programlisting>
+ Import-Package: com.acme.foo;version="[1.23, 2)", com.acme.bar;version="[4.0, 5.0)"
+ </programlisting>
+
+ <para>With the OSGi Class Loading Architecture many bundles can share a single virtual machine (VM).
+ Within this VM, bundles can hide packages and classes from other bundles, as well as share packages with other bundles.</para>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/osgi-classloader.png"/>
+ </imageobject>
+ </mediaobject>
+
+ <para>For example, the following import and export definition resolve correctly because the version range in the import definition
+ matches the version in the export definition:</para>
+
+ <programlisting>
+ A: Import-Package: p; version="[1,2)"
+ B: Export-Package: p; version=1.5.1
+ </programlisting>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/osgi-version-constraint.png"/>
+ </imageobject>
+ </mediaobject>
+
+ <para>Appart from bundle versions, OSGi Attribute Matching is a generic mechanism to allow the importer and exporter to influence the
+ matching process in a declarative way. For example, the following statements will match.</para>
- <itemizedlist>
- <listitem><para>A set of services that an OSGi container must implement</para></listitem>
- <listitem><para>A contract between the container and your application</para></listitem>
- </itemizedlist>
+ <programlisting>
+ A: Import-Package: com.acme.foo;company=ACME
+ B: Export-Package: com.acme.foo;company=ACME; security=false
+ </programlisting>
- <para>Developing on the OSGi platform means first building your application using OSGi APIs, then deploying it in an OSGi container.</para>
+ <para>An exporter can limit the visibility of the classes in a package with the include and exclude directives on the export definition.</para>
+
+ <programlisting>
+ Export-Package: com.acme.foo; include:="Qux*,BarImpl"; exclude:=QuxImpl
+ </programlisting>
+ </sect2>
+
+ <sect2>
+ <title>OSGi Life Cycle Layer</title>
+
+ <para>The Life Cycle Layer provides an API to control the security and life cycle operations of bundles.</para>
+
+ <para>A bundle can be in one of the following states:</para>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/osgi-life-cycle.png"/>
+ </imageobject>
+ </mediaobject>
+
+ <para>A bundle is activated by calling its <emphasis role="bold">Bundle Activator</emphasis> object, if one exists.
+ The BundleActivator interface defines methods that the Framework invokes when it starts and stops the bundle.</para>
+
+ <para>A Bundle Context object represents the execution context of a single bundle within the OSGi Service Platform,
+ and acts as a proxy to the underlying Framework. A <emphasis role="bold">Bundle Context</emphasis> object is created by the Framework when a bundle is started.
+ The bundle can use this private BundleContext object for the following purposes:</para>
+
+ <itemizedlist>
+ <listitem>Installing new bundles into the OSGi environment</listitem>
+ <listitem>Interrogating other bundles installed in the OSGi environment</listitem>
+ <listitem>Obtaining a persistent storage area</listitem>
+ <listitem>Retrieving service objects of registered services</listitem>
+ <listitem>Registering services in the Framework service</listitem>
+ <listitem>Subscribing or unsubscribing to Famework events</listitem>
+ </itemizedlist>
+
+ </sect2>
+
+ <sect2>
+ <title>OSGi Service Layer</title>
+
+ <para>The OSGi Service Layer defines a dynamic collaborative model that is highly integrated with the Life Cycle Layer.
+ The service model is a publish, find and bind model. A service is a normal Java object that is registered under one or more
+ Java interfaces with the service registry.</para>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/osgi-service-registration.png"/>
+ </imageobject>
+ </mediaobject>
+ </sect2>
+ </sect1>
+ <sect1>
+ <title>OSGi Service Compendium</title>
+ <para>The OSGi Service Compendium specifies a number of services that may be available in an OSGi runtime environment.
+ Although the OSGi Framework specification is useful in itself already, it only defines the OSGi core infrastructure.
+ The services defined in the compendium specification define the scope and functionality of some common services that
+ bundle developers might want to use. Here is a quick summary:</para>
+
+ <sect2>
+ <title>Log Service</title>
+ <para>The Log Service provides a general purpose message logger for the OSGi Service Platform. It consists of two services,
+ one for logging information and another for retrieving current or previously recorded log information.</para>
+ </sect2>
+
+ <sect2>
+ <title>Http Service</title>
+ <para>The Http Service supports two standard techniques for registering servlets and resources to develop communication and
+ user interface solutions for standard technologies such as HTTP, HTML, XML, etc.</para>
+ </sect2>
+
+ <sect2>
+ <title>Device Access Specification</title>
+ <para>The Device Access specification supports the coordination of automatic detection and attachment of existing devices on
+ an OSGi Service Platform, facilitates hot-plugging and -unplugging of new devices, and downloads and installs device drivers on demand.</para>
+ </sect2>
+
+ <sect2>
+ <title>Configuration Admin Service</title>
+ <para>The Configuration Admin service allows an Operator to set the configuration information of deployed bundles.</para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/osgi-config-service.png" contentwidth="450"/>
+ </imageobject>
+ </mediaobject>
+ </sect2>
+
+ <sect2>
+ <title>Metatype Service</title>
+ <para>The Metatype Service specification defines interfaces that allow bundle developers to describe attribute
+ types in a computer readable form using so-called metadata.</para>
+ </sect2>
+
+ <sect2>
+ <title>Preferences Service</title>
+ <para>The Preferences Service allows storage of data that is specific to a particular user.</para>
+ </sect2>
+
+ <sect2>
+ <title>User Admin Service</title>
+ <para>Bundles can use the User Admin Service to authenticate an initiator and represent this authentication as an Authorization object.
+ Bundles that execute actions on behalf of this user can use the Authorization object to verify if that user is authorized.</para>
+ </sect2>
+
+ <sect2>
+ <title>Wire Admin Service</title>
+ <para>The Wire Admin Service is an administrative service that is used to control a wiring topology in the OSGi Service Platform.
+ It is intended to be used by user interfaces or management programs that control the wiring of services in an OSGi Service Platform.</para>
+ </sect2>
+
+ <sect2>
+ <title>IO Connector Service</title>
+ <para>The IO Connector Service specification adopts the Java 2 Micro Edition (J2ME) javax.microedition.io packages as a basic communications
+ infrastructure.</para>
+ </sect2>
+
+ <sect2>
+ <title>UPnP Device Service</title>
+ <para>The UPnP Device Service specifies how OSGi bundles can be developed that interoperate with UPnP (Universal Plug and Play)
+ devices and UPnP control points.</para>
+ </sect2>
+
+ <sect2>
+ <title>Declarative Services Specification</title>
+ <para>The Declarative Services specification addresses some of the complications that arise when the OSGi service model is
+ used for larger systems and wider deployments, such as: Startup Time, Memory Footprint, Complexity. The service component
+ model uses a declarative model for publishing, finding and binding to OSGi services.</para>
+ </sect2>
+
+ <sect2>
+ <title>Event Admin Service</title>
+ <para>The Event Admin Service provides an inter-bundle communication mechanism. It is based on a event publish and subscribe model, popular in many message based systems.</para>
+ </sect2>
+
+ <sect2>
+ <title>Deployment Admin Service</title>
+ <para>The Deployment Admin Service specification, standardizes the access to some of the responsibilities of the management agent:
+ that is, the lifecycle management of interlinked resources on an OSGi Service Platform.</para>
+ </sect2>
+
+ <sect2>
+ <title>Auto Configuration Specification</title>
+ <para>The Auto Configuration Specification is to allow the configuration of bundles.
+ These bundles can be embedded in Deployment Packages or bundles that are already present on the OSGi Service Platform.</para>
+ </sect2>
+
+ <sect2>
+ <title>Application Admin Service</title>
+ <para>The Application Admin Service is intended to simplify the management of an environment with many different types of applications
+ that are simultaneously available.</para>
+ </sect2>
+
+ <sect2>
+ <title>DMT Admin Service</title>
+ <para>The DMT Admin Service specification defines an API for managing a device using concepts from the OMA DM specifications.</para>
+ </sect2>
+
+ <sect2>
+ <title>Monitor Admin Service</title>
+ <para>The Monitor Admin Service specification outlines how a bundle can publish Status Variables and how administrative bundles
+ can discover Status Variables as well as read and reset their values.</para>
+ </sect2>
+
+ <sect2>
+ <title>Foreign Application Access Specification</title>
+ <para>The Foreign Application Access specification is to enable foreign application models like MIDP, Xlets, Applets, other Java
+ application models to participate in the OSGi service oriented architecture.</para>
+ </sect2>
+
+ <sect2>
+ <title>Service Tracker Specification</title>
+ <para>The Service Tracker specification defines a utility class, ServiceTracker, that makes tracking the registration, modification,
+ and unregistration of services much easier.</para>
+ </sect2>
+
+ <sect2>
+ <title>XML Parser Service Specification</title>
+ <para>The XML Parser Service specification addresses how the classes defined in JAXP can be used in an OSGi Service Platform.</para>
+ </sect2>
+
+ <sect2>
+ <title>Position Specification</title>
+ <para>The Position Specification provides bundle developers with a consistent way of handling geographic positions in OSGi applications.</para>
+ </sect2>
+
+ <sect2>
+ <title>Measurement and State Specification</title>
+ <para>The Measurement and State Specification provides a consistent way of handling a diverse range of measurements for bundle developers.</para>
+ </sect2>
+
+ <sect2>
+ <title>Execution Environment Specification</title>
+ <para>This Execution Environment Specification defines different execution environments for OSGi Server Platform Servers.</para>
+ </sect2>
+ </sect1>
+
</chapter>
Added: projects/jboss-osgi/trunk/build/docbook/en/modules/providedservices.xml
===================================================================
--- projects/jboss-osgi/trunk/build/docbook/en/modules/providedservices.xml (rev 0)
+++ projects/jboss-osgi/trunk/build/docbook/en/modules/providedservices.xml 2009-03-23 15:12:01 UTC (rev 86210)
@@ -0,0 +1,25 @@
+<chapter id="Chap_Provided_Services">
+
+ <title>Provided Services</title>
+
+ <section id="Sec_Web_Console_Service">
+ <title>Web Console Service</title>
+ <para>TODO</para>
+ </section>
+
+ <section id="Sec_Logging_Service">
+ <title>Logging Service</title>
+ <para>TODO</para>
+ </section>
+
+ <section id="Sec_Http_Service">
+ <title>Http Service</title>
+ <para>TODO</para>
+ </section>
+
+ <section id="Sec_Config_Admin_Service">
+ <title>Config Admin Service</title>
+ <para>TODO</para>
+ </section>
+
+</chapter>
Property changes on: projects/jboss-osgi/trunk/build/docbook/en/modules/providedservices.xml
___________________________________________________________________
Name: svn:keywords
+ Id Revision
Name: svn:eol-style
+ LF
Modified: projects/jboss-osgi/trunk/build/docbook/pom.xml
===================================================================
--- projects/jboss-osgi/trunk/build/docbook/pom.xml 2009-03-23 15:11:04 UTC (rev 86209)
+++ projects/jboss-osgi/trunk/build/docbook/pom.xml 2009-03-23 15:12:01 UTC (rev 86210)
@@ -71,11 +71,6 @@
-->
<formats>
<format>
- <formatName>pdf</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-pdf.xsl</stylesheetResource>
- <finalName>${pom.name}.pdf</finalName>
- </format>
- <format>
<formatName>html</formatName>
<stylesheetResource>classpath:/xslt/org/jboss/main-html.xsl</stylesheetResource>
<finalName>index.html</finalName>
@@ -85,6 +80,11 @@
<stylesheetResource>classpath:/xslt/org/jboss/nochunk-html.xsl</stylesheetResource>
<finalName>index.html</finalName>
</format>
+ <format>
+ <formatName>pdf</formatName>
+ <stylesheetResource>classpath:/xslt/org/jboss/main-pdf.xsl</stylesheetResource>
+ <finalName>${pom.name}.pdf</finalName>
+ </format>
</formats>
<options>
<xincludeSupported>true</xincludeSupported>
More information about the jboss-cvs-commits
mailing list