[jboss-cvs] JBossAS SVN: r82613 - projects/docs/community/5/Administration_And_Configuration_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Jan 5 12:58:50 EST 2009
Author: smcgowan at redhat.com
Date: 2009-01-05 12:58:50 -0500 (Mon, 05 Jan 2009)
New Revision: 82613
Modified:
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/AOP.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Architecture.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Cache.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JBoss_Cache_JGroups.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JMS.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/EJB3.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/FAQ.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/General_Configuration.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/JGroups.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Messaging.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Performance_Tuning.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Pooling.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Remoting.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Security.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Transactions.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Virtual_Deployment_Framework.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Web_Services.xml
Log:
JBAS-6325 - first pass
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/AOP.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/AOP.xml 2009-01-05 17:10:19 UTC (rev 82612)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/AOP.xml 2009-01-05 17:58:50 UTC (rev 82613)
@@ -2,9 +2,12 @@
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [ ]>
<chapter id="jboss_aop">
-<title>JBOSS AOP</title>
+<title>JBoss AOP</title>
-<para>JBoss AOP is a 100% Pure Java Aspected Oriented Framework usable in any programming environment or tightly integrated with our application server. Aspects allow you to more easily modularize your code base when regular object oriented programming just doesn't fit the bill. It can provide a cleaner separation from application logic and system code. It provides a great way to expose integration points into your software. Combined with JDK 1.5 Annotations, it also is a great way to expand the Java language in a clean pluggable way rather than using annotations solely for code generation. </para>
+<para>
+ <indexterm><primary>JBoss AOP</primary><secondary>aspect oriented framework</secondary></indexterm>
+ <indexterm><primary>AOP</primary><see>JBoss AOP</see></indexterm>
+ JBoss AOP is a 100% Pure Java Aspected Oriented Framework usable in any programming environment or tightly integrated with our application server. Aspects allow you to more easily modularize your code base when regular object oriented programming just doesn't fit the bill. It can provide a cleaner separation from application logic and system code. It provides a great way to expose integration points into your software. Combined with JDK 1.5 Annotations, it also is a great way to expand the Java language in a clean pluggable way rather than using annotations solely for code generation. </para>
<para>JBoss AOP is not only a framework, but also a prepackaged set of aspects that are applied via annotations, pointcut expressions, or dynamically at runtime. Some of these include caching, asynchronous communication, transactions, security, remoting, and many many more. </para>
@@ -91,6 +94,7 @@
<section>
<title>Creating Aspects in JBoss AOP</title>
<para>
+ <indexterm><primary>JBoss AOP</primary><secondary>creating aspects</secondary></indexterm>
In short, all AOP frameworks define two things: a way to implement crosscutting concerns, and a programmatic construct -- a programming language or a set of tags -- to specify how you want to apply those snippets of code.
Let's take a look at how JBoss AOP, its cross-cutting concerns, and how you can implement a metrics aspect in JBoss.
</para>
@@ -133,6 +137,7 @@
<section>
<title>Applying Aspects in JBoss AOP</title>
<para>
+ <indexterm><primary>JBoss AOP</primary><secondary>applying aspects</secondary></indexterm>
To apply an aspect, you define when to execute the aspect code. Those points in execution are called pointcuts. An analogy to a pointcut is a regular expression. Where a regular expression matches strings, a pointcut expression matches events/points within your application. For example, a valid pointcut definition would be "for all calls to the JDBC method executeQuery(), call the aspect that verifies SQL syntax."
</para>
<para>
@@ -167,4 +172,4 @@
Just as important, orthogonal behavior could be bolted on after development. In Listing One, monitoring and profiling must be added at development time. With AOP, a developer or an administrator can (easily) add monitoring and metrics as needed without touching the code. This is a very subtle but significant part of AOP, as this separation (obliviousness, some may say) allows aspects to be layered on top of or below the code that they cut across. A layered design allows features to be added or removed at will. For instance, perhaps you snap on metrics only when you're doing some benchmarks, but remove it for production. With AOP, this can be done without editing, recompiling, or repackaging the code.
</para>
</section>
-</chapter>
\ No newline at end of file
+</chapter>
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Architecture.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Architecture.xml 2009-01-05 17:10:19 UTC (rev 82612)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Architecture.xml 2009-01-05 17:58:50 UTC (rev 82613)
@@ -5,6 +5,7 @@
<chapter id="JBoss_AS5_Architecture">
<title>JBoss Application Server 5 architecture</title>
<para>
+ <indexterm><primary>JBossAS</primary><secondary>architecture</secondary></indexterm>
The following diagram illustrates an overview of the JBoss.org community projects including the JBoss Appplication Server and its components.
<inlinemediaobject>
<imageobject>
@@ -170,4 +171,4 @@
<para>Disabling hot deployment simply entails removing the hdscanner-jboss-beans.xml deployment.</para>
</sect1>
-</chapter>
\ No newline at end of file
+</chapter>
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Cache.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Cache.xml 2009-01-05 17:10:19 UTC (rev 82612)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Cache.xml 2009-01-05 17:58:50 UTC (rev 82613)
@@ -5,13 +5,17 @@
<chapter id="jboss_cache">
<title>JBoss Cache</title>
<section><title>What is JBoss Cache?</title>
- <para>JBoss Cache is a tree-structured, clustered, transactional cache. It is the backbone for many fundamental JBoss Application Server clustering services, including - in certain versions - clustering JNDI, HTTP and EJB sessions. </para>
+ <para>
+ <indexterm><primary>JBoss Cache</primary><secondary>about</secondary></indexterm>
+ JBoss Cache is a tree-structured, clustered, transactional cache. It is the backbone for many fundamental JBoss Application Server clustering services, including - in certain versions - clustering JNDI, HTTP and EJB sessions. </para>
<para>JBoss Cache can also be used as a standalone transactional and clustered caching library or even an object oriented data store. It can even be embedded in other enterprise Java frameworks and application servers such as BEA WebLogic or IBM WebSphere, Tomcat, Spring, Hibernate, and many others. It is also very commonly used directly by standalone Java applications that do not run from within an application server, to maintain clustered state. </para>
</section>
<section>
<title>And what is Pojo Cache?</title>
- <para>Pojo Cache is an extension of the core JBoss Cache API. Pojo Cache offers additional functionality such as: </para>
+ <para>
+ <indexterm><primary>JBoss Cache</primary><secondary>Pojo Cache</secondary></indexterm>
+ Pojo Cache is an extension of the core JBoss Cache API. Pojo Cache offers additional functionality such as: </para>
<orderedlist>
<listitem>
<para>maintaining object references even after replication or persistence. </para>
@@ -63,6 +67,7 @@
<section>
<title>Running JBoss Cache in the JBoss Application server</title>
<para>
+ <indexterm><primary>JBossAS</primary><secondary>running JBoss Cache with JBossAS</secondary></indexterm>
JBoss Cache uses JGroups as a transport layer. More information on JGroups can be found on <xref linkend="jgroups"/>
</para>
@@ -716,4 +721,4 @@
</orderedlist>
</para>
</section>
-</chapter>
\ No newline at end of file
+</chapter>
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JBoss_Cache_JGroups.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JBoss_Cache_JGroups.xml 2009-01-05 17:10:19 UTC (rev 82612)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JBoss_Cache_JGroups.xml 2009-01-05 17:58:50 UTC (rev 82613)
@@ -3,7 +3,10 @@
<chapter id="jbosscache.chapt">
<title>JBossCache and JGroups Services</title>
- <para>JGroups and JBossCache provide the underlying communication, node replication and caching services, for
+ <para>
+ <indexterm><primary>Clustering</primary><secondary>JBossCache and JGroups Services</secondary></indexterm>
+
+JGroups and JBossCache provide the underlying communication, node replication and caching services, for
JBoss AS clusters. Those services are configured as MBeans. There is a set of JBossCache and JGroups MBeans
for each type of clustering applications (e.g., the Stateful Session EJBs, HTTP session replication etc.).
</para>
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JMS.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JMS.xml 2009-01-05 17:10:19 UTC (rev 82612)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JMS.xml 2009-01-05 17:58:50 UTC (rev 82613)
@@ -6,6 +6,7 @@
<section><title>Unique server peer id</title>
<para>
+ <indexterm><primary>Clustering</primary><secondary>JBoss Messaging Clustering Notes</secondary></indexterm>
JBoss Messaging clustering should work out of the box in the <emphasis>all</emphasis> configuration with no configuration changes. It is however crucial that every node is assigned a unique server id.
</para>
<para>
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/EJB3.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/EJB3.xml 2009-01-05 17:10:19 UTC (rev 82612)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/EJB3.xml 2009-01-05 17:58:50 UTC (rev 82613)
@@ -5,7 +5,10 @@
<chapter id="EJB3_Services">
<title>Enterprise Applications with EJB3 Services</title>
- <para>EJB3 (Enterprise Java Bean 3.0) provides the core component model for Java EE 5 applications. An EJB3 bean is a managed component that is automatically wired to take advantage of all services the Java EE 5 server container provides, such as transaction, security, persistence, naming, dependency injection, etc. The managed component allows developers to focus on the business logic, and leave the cross-cutting concerns to the container as configurations. As an application developer, you need not create or destroy the components yourself. You only need to ask for an EJB3 bean from the Java EE container by its name, and then you can call its methods with all configured container services applied. You can get access to an EJB3 bean from either inside or outside of the Java EE container. </para>
+ <para>
+ <indexterm><primary>>Enterprise Applications with EJB3 Services</primary><secondary>Enterprise JavaBean 3.0</secondary></indexterm>
+ <indexterm><primary>EJB3</primary><see>Enterprise Applications with EJB3 Services</see></indexterm>
+ EJB3 (Enterprise Java Bean 3.0) provides the core component model for Java EE 5 applications. An EJB3 bean is a managed component that is automatically wired to take advantage of all services the Java EE 5 server container provides, such as transaction, security, persistence, naming, dependency injection, etc. The managed component allows developers to focus on the business logic, and leave the cross-cutting concerns to the container as configurations. As an application developer, you need not create or destroy the components yourself. You only need to ask for an EJB3 bean from the Java EE container by its name, and then you can call its methods with all configured container services applied. You can get access to an EJB3 bean from either inside or outside of the Java EE container. </para>
<para>JBoss AS 5 supports EJB3 out of the box. Note that JBoss AS 4.2 is a J2EE server, so it does not support the full EJB3 feature set. </para>
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/FAQ.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/FAQ.xml 2009-01-05 17:10:19 UTC (rev 82612)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/FAQ.xml 2009-01-05 17:58:50 UTC (rev 82613)
@@ -6,6 +6,7 @@
<title>Frequently Asked Questions</title>
<section><title>I have problems with Oracle XA?</title>
<para>
+ <indexterm><primary>Frequently Asked Questions</primary></indexterm>
Check that you:
<orderedlist>
<listitem>
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/General_Configuration.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/General_Configuration.xml 2009-01-05 17:10:19 UTC (rev 82612)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/General_Configuration.xml 2009-01-05 17:58:50 UTC (rev 82613)
@@ -4,6 +4,7 @@
<chapter id="general_config">
<title>General Configuration</title>
<para>This chapter covers general configuration issues for the JBoss Application Server.
+ <indexterm><primary>JBossAS</primary><secondary>General Configuration</secondary></indexterm>
</para>
<section><title>Configuring Multiple JBoss Instances On One Machine</title>
@@ -52,4 +53,4 @@
</section>
-</chapter>
\ No newline at end of file
+</chapter>
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/JGroups.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/JGroups.xml 2009-01-05 17:10:19 UTC (rev 82612)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/JGroups.xml 2009-01-05 17:58:50 UTC (rev 82613)
@@ -5,6 +5,7 @@
<chapter id="jgroups"><title>JGroups</title>
<para>
+ <indexterm><primary>JGroups</primary><secondary>multicast communication toolkit</secondary></indexterm>
JBoss AS clustering is built on JGroups - a toolkit for reliable multicast communication between AS server nodes on an existing computer network. It can be used to create groups of processes whose members can send messages to each other. JGroups enables developers to create reliable multipoint (multicast) applications where reliability is a deployment issue. JGroups also relieves the application developer from implementing this logic themselves. This saves significant development time and allows for the application to be deployed in different environments without having to change code. The following are the key features of JGroup.
</para>
@@ -68,4 +69,4 @@
</section>
-</chapter>
\ No newline at end of file
+</chapter>
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Messaging.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Messaging.xml 2009-01-05 17:10:19 UTC (rev 82612)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Messaging.xml 2009-01-05 17:58:50 UTC (rev 82613)
@@ -3,7 +3,10 @@
]>
<chapter id="messaging"><title>JBoss Messaging</title>
-<para>JBoss Messaging is the new enterprise messaging system from JBoss. It is a complete rewrite of JBossMQ, the legacy JBoss JMS provider. It is the default JMS provider on JBoss AS 5. Production support is already available through JBoss EAP 4.3, and we offer developer support for JBoss 4.2.x.</para>
+<para>
+ <indexterm><primary>JBoss Messaging</primary><secondary>about</secondary></indexterm>
+ <indexterm><primary>JMS</primary><see>JBoss Messaging</see></indexterm>
+JBoss Messaging is the new enterprise messaging system from JBoss. It is a complete rewrite of JBossMQ, the legacy JBoss JMS provider. It is the default JMS provider on JBoss AS 5. Production support is already available through JBoss EAP 4.3, and we offer developer support for JBoss 4.2.x.</para>
<para>JBoss Messaging is a high Performance JMS 1.1 compliant implementation integrated with JBoss Transactions. It also offers:
<itemizedlist>
<listitem>
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Performance_Tuning.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Performance_Tuning.xml 2009-01-05 17:10:19 UTC (rev 82612)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Performance_Tuning.xml 2009-01-05 17:58:50 UTC (rev 82613)
@@ -7,6 +7,9 @@
<title>Introduction</title>
<para>
+ <indexterm><primary>JBoss AS 5 Performance Tuning</primary><secondary>performance</secondary></indexterm>
+ <indexterm><primary>Performance</primary><secondary>JBoss AS 5 Performance Tuning</secondary></indexterm>
+ <indexterm><primary>JBossAS</primary><secondary>performance tuning</secondary></indexterm>
Developing applications and deploying them to an application server does not guarantee best performance without performance tuning of the applications and server.
Performance tuning involves ensuring your application does not consume resources unnecessarily while ensures best performance of the applications and application server.
</para>
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Pooling.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Pooling.xml 2009-01-05 17:10:19 UTC (rev 82612)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Pooling.xml 2009-01-05 17:58:50 UTC (rev 82613)
@@ -6,6 +6,7 @@
<title>Pooling</title>
<section><title>Strategy</title>
<para>
+ <indexterm><primary>Pooling</primary><secondary>JBossJCA</secondary></indexterm>
<ulink url="http://www.jboss.org/wiki/JBossJCA">JBossJCA</ulink> uses a <literal>ManagedConnectionPool</literal> to perform the pooling. The <literal>ManagedConnectionPool</literal> is made up of subpools depending upon the strategy chosen and other pooling parameters.
</para>
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Remoting.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Remoting.xml 2009-01-05 17:10:19 UTC (rev 82612)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Remoting.xml 2009-01-05 17:58:50 UTC (rev 82613)
@@ -5,6 +5,7 @@
<chapter id="remoting"><title>Remoting</title>
<para>
+ <indexterm><primary>Remoting</primary><secondary>about</secondary></indexterm>
The main objective of JBoss Remoting is to provide a single API for most network based invocations and related service that uses pluggable transports and data marshallers. The JBoss Remoting API provides the ability for making synchronous and asynchronous remote calls, push and pull callbacks, and automatic discovery of remoting servers. The intention is to allow for the addition of different transports to fit different needs, yet still maintain the same API for making the remote invocations and only requiring configuration changes, not code changes, to fit these different needs.
</para>
<para>
@@ -160,4 +161,4 @@
</section>
-</chapter>
\ No newline at end of file
+</chapter>
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Security.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Security.xml 2009-01-05 17:10:19 UTC (rev 82612)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Security.xml 2009-01-05 17:58:50 UTC (rev 82613)
@@ -3,6 +3,8 @@
]>
<chapter id="security">
<title>Security</title>
+ <indexterm><primary>Security</primary><secondary>JBossAS</secondary></indexterm>
+ <indexterm><primary>JBossAS</primary><secondary>Security</secondary></indexterm>
<para>The JBoss security framework default implementation is based on JAAS. It implements standard J2EE authentication and authorization but also supports extended security models with <ulink url="http://wiki.jboss.org/wiki/Edit.jsp?page=SecurityProxy">SecurityProxy?</ulink> and <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=SecurityAssociation">SecurityAssociation</ulink> implementations. </para>
<para>JAAS based implementation enables pluggable authentication modules (PAMs) which is a way to integrate with existing authentication frameworks in your enterprise. </para>
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Transactions.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Transactions.xml 2009-01-05 17:10:19 UTC (rev 82612)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Transactions.xml 2009-01-05 17:58:50 UTC (rev 82613)
@@ -3,7 +3,10 @@
]>
<chapter id="transaction"><title>JBoss Transactions</title>
-<para>JBoss Transactions runs in the <emphasis>all</emphasis> server configurations or customized configurations based on the <emphasis>all</emphasis> configuration. </para>
+<para>
+ <indexterm><primary>JBossAS</primary><secondary>transactions</secondary></indexterm>
+ <indexterm><primary>JBoss Transactions</primary></indexterm>
+JBoss Transactions runs in the <emphasis>all</emphasis> server configurations or customized configurations based on the <emphasis>all</emphasis> configuration. </para>
<figure id="transactions_architecture">
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Virtual_Deployment_Framework.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Virtual_Deployment_Framework.xml 2009-01-05 17:10:19 UTC (rev 82612)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Virtual_Deployment_Framework.xml 2009-01-05 17:58:50 UTC (rev 82613)
@@ -5,6 +5,8 @@
<chapter id="virtual_deployment_framework">
<title>JBoss5 Virtual Deployment Framework</title>
<para>
+ <indexterm><primary>JBoss5 Virtual Deployment Framework</primary><secondary>virtual deployment framework</secondary></indexterm>
+ <indexterm><primary>Virtual Deployment Framework</primary><see>JBoss5 Virtual Deployment Framework</see></indexterm>
As indicated in <xref linkend="JBoss_AS5_Introduction"/> the JBoss Application Server 5 is designed around the advanced concept of a Virtual Deployment Framework (VDF). This chapter discusses the JBoss5 Virtual Deployment Framework further. The following UML diagram illustrates an overview of the key JBoss5 Deployment Framework classes.
<figure id="JBoss5_virtual_deployment_framework_diagram">
@@ -27,7 +29,8 @@
<itemizedlist>
<listitem>
- <para><emphasis>StructureDeployers</emphasis> used to analyze the structure of a DeploymentContext when addDeploymentContext(DeploymentContext) is invoked. For each StructureDeployer the determineStructure(DeploymentContext) method is invoked to analyze the deployment. A StructureDeployer returns true to indicate that the deployment was recognized and no further StructureDeployer should analyze the DeploymentContext.
+ <para>
+ <emphasis>StructureDeployers</emphasis> used to analyze the structure of a DeploymentContext when addDeploymentContext(DeploymentContext) is invoked. For each StructureDeployer the determineStructure(DeploymentContext) method is invoked to analyze the deployment. A StructureDeployer returns true to indicate that the deployment was recognized and no further StructureDeployer should analyze the DeploymentContext.
</para>
</listitem>
</itemizedlist>
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Web_Services.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Web_Services.xml 2009-01-05 17:10:19 UTC (rev 82612)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Web_Services.xml 2009-01-05 17:58:50 UTC (rev 82613)
@@ -5,6 +5,10 @@
<chapter id="Web_Services">
<title>Web Services</title>
<para>
+ <indexterm><primary>Web Services</primary><secondary>web services</secondary></indexterm>
+ <indexterm><primary>JBossWS</primary><secondary>Web Services</secondary></indexterm>
+ <indexterm><primary>JAX-WS</primary><see>Web Services</see></indexterm>
+
Web services are a key contributing factor in the ways Web commerce is conducted today.
Web services enable application/programs to communicate by sending small and large chunks of data to each other.
</para>
More information about the jboss-cvs-commits
mailing list