[jboss-svn-commits] JBL Code SVN: r36515 - in labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US: extras and 3 other directories.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Mon Jan 10 19:25:55 EST 2011
Author: dlesage
Date: 2011-01-10 19:25:55 -0500 (Mon, 10 Jan 2011)
New Revision: 36515
Added:
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/invm/
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/invm/Code_Example7.xmlt
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/invm/Code_Example9.xmlt
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/invm/Code_example_invm_passbyvalue.xmlt
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/invm/inVM_example1.xmlt
Modified:
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Advanced_Topics.xml
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Building_and_Using_Services.xml
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Configuration.xml
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/JBossESB.xml
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Legal_Notice.xml
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Other_Components.xml
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Revision_History.xml
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Service_Orientated_Architecture_Overview.xml
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Services_and_Messages.xml
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/building_and_using_services/Code_Example6.xmlt
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/building_and_using_services/annotate3.xmlt
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/building_and_using_services/annotate7.java
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/services_and_messages/code1.xmlt
Log:
SOA-2183 Merges from product doc QE process.
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Advanced_Topics.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Advanced_Topics.xml 2011-01-11 00:14:47 UTC (rev 36514)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Advanced_Topics.xml 2011-01-11 00:25:55 UTC (rev 36515)
@@ -76,7 +76,7 @@
<classname>SystemPrintln</classname>, which is the first
action in the <systemitem>pipeline</systemitem>.
</para>
-
+<!-- REMOVED SOA 2036
<note>
<para>
Because the <classname>ServiceInvoker</classname> hides
@@ -89,7 +89,7 @@
of service fail-over.
</para>
</note>
-
+-->
</section>
<section>
@@ -458,12 +458,12 @@
</listitem>
</orderedlist>
-
+ <!--
<para>
- Scheduling is new to 4.2 of the ESB and not all of the
- listeners have been migrated over to this model yet.
+ Scheduling is new to the JBoss ESB and not all of the listeners
+ have been migrated over to this model yet.
</para>
-
+ -->
<para>
JBoss ESB offers a <schedule-listener> as well as 2 <schedule-provider>
types: <simple-schedule> and <cron-schedule>. The <schedule-listener> is
@@ -777,7 +777,6 @@
scheduled-listener is configured with an “event-processor” class, which can be an implementation of one of the following interfaces:
</para>
<itemizedlist>
-<listitem><para></para></listitem>
<listitem><para>ScheduledEventListener: Event Processors that implement this interface are simply triggered through the “onSchedule” method. No action processing pipeline is executed.</para></listitem>
<listitem><para>ScheduledEventMessageComposer: Event Processors that implement this interface are capable of “composing” a message for the action processing pipeline associated with the listener.</para></listitem>
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Building_and_Using_Services.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Building_and_Using_Services.xml 2011-01-11 00:14:47 UTC (rev 36514)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Building_and_Using_Services.xml 2011-01-11 00:25:55 UTC (rev 36515)
@@ -130,7 +130,7 @@
of which is obtained by calling
<methodname>toString()</methodname> on the payload.)
</para>
-
+<!--
<note>
<para>
The <classname>JMSNotifier</classname> previously sent
@@ -155,7 +155,7 @@
from relying upon defaults.
</para>
</note>
-
+-->
<para>
As outlined above, it is a
<systemitem>listener</systemitem>'s responsibilities to act
@@ -495,7 +495,7 @@
clean <systemitem>action</systemitem> implementations.
This hides the complexity associated with implementing
interfaces, abstract classes and dealing with the
- <systemitem>ConfigTree</systemitem> type.
+ <systemitem>ConfigTree</systemitem> type (the configuration information provided in the <filename>jboss-esb.xml</filename> file).
</para>
<para>
@@ -558,11 +558,6 @@
</listitem>
- <listitem>
- <para>
- @Process
- </para>
- </listitem>
</itemizedlist>
@@ -572,7 +567,7 @@
@Process
</title>
<para>
- The simplest implementation involves creating
+ The simplest implementation involves creating an action with a
a basic <firstterm>plain old Java object</firstterm> (POJO)
with a single method, annotated with @Process:
</para>
@@ -582,7 +577,7 @@
<para>
The @Process annotation serves to identify the class as a valid
ESB <systemitem>action</systemitem>. In cases in which there
- are multiple methods in the class, it also identifies the one
+ are multiple methods in the class, it also identifies the method
which is to be used for processing the message instance (or
some part of the message. This is explained in more depth when
the @BodyParam, @PropertyParam and @AttachmentParam annotations
@@ -634,7 +629,7 @@
<listitem>
<para>
message: This is an ESB message instance. This
- becomes the active/current instance on <systemitem>action
+ becomes the active/current instance on the <systemitem>action
pipeline</systemitem>.
</para>
</listitem>
@@ -651,7 +646,11 @@
</para>
</listitem>
</itemizedlist>
-
+</section>
+<section>
+ <title>
+ @Process Method Parameters
+ </title>
<para>
Use @Process methods to specify parameters in a range of
different ways. One can:
@@ -742,8 +741,8 @@
</title>
<para>
- One will have to configure most of the actions to some
- degree. In the ESB action configuration, the properties are
+ Most actions require some degree of custom configuration.
+ In the ESB action configuration, the properties are
supplied as <property> sub-elements of the
<action> element:
</para>
@@ -751,7 +750,7 @@
<programlisting language="XML" role="XML"><xi:include href="extras/building_and_using_services/annotate8.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
<para>
- In order to utilise these properties, use the low/base level
+ In order to utilise these properties, one must use the low/base level
action implementations (do so by extending
<classname>AbstractActionPipelineProcessor</classname> or by
implementing <classname>ActionLifecycle</classname>.) This
@@ -812,7 +811,7 @@
<para>
Whilst the tasks above are generally not difficult to
- undertake, they can be a tad laborious, error-prone and
+ undertake, they can be laborious, error-prone and
lead to inconsistencies across actions with regard to how
configuration mistakes are handled. One may also be
required to add quite a lot of code, with a net result of
@@ -832,7 +831,7 @@
<note>
<para>
One can also define the @ConfigProperty annotation on
- "setter" methods (<literal>V</literal>s on the field.)
+ "setter" methods (as opposed to on the field.)
</para>
</note>
@@ -842,9 +841,9 @@
implementation and the maps found within the decoded value
(including any support for enums, as with the LogLevel enum
above.) It finds the action fields possessing the
- @ConfigProperty annotation. Hence the developer is not
+ @ConfigProperty annotation. The developer is not
required to deal with the <classname>ConfigTree</classname>
- class at all or develop any convoluted code.
+ class at all or develop any extra code.
</para>
<para>
@@ -928,7 +927,7 @@
<para>
The bean configuration's property values are decoded from
- their string values. To then matched them against the
+ their string values. To then match them against the
appropriate POJO bean property type, these simple rules are
used:
</para>
@@ -964,7 +963,7 @@
<para>
Sometimes action implementations need to perform
- initialization task at deployment time. They may also need to
+ initialization tasks at deployment time. They may also need to
perform a clean-up whilst being undeployed. For these
reasons, there are @Initialize and @Destroy method
annotations.
@@ -984,7 +983,7 @@
<note>
<para>
- All of the @ConfigProperty annotations have been processed by the
+ All of the @ConfigProperty annotations will have been processed by the
time the ESB deployer invokes the @Initialize methods.
Therefore, the @Initialize methods can rely on these fields
being ready before they execute the customised
@@ -994,7 +993,7 @@
<note>
<para>
- There is no need to use both of these annotations to specify
+ There is no need to always use both of these annotations to specify
methods. Only specify them if there is a need; in other
words, if a method only needs initialization, only use the
@Initialize annotation (one does not have to supply a
@@ -1013,7 +1012,7 @@
<para>
One can optionally specify a
<classname>ConfigTree</classname> parameter on @Initialize
- methods. Do this to have access to the actions which underlie
+ methods. Do this to have access to the actions which underlie that
<classname>ConfigTree</classname> instance.
</para>
</note>
@@ -1025,7 +1024,7 @@
</title>
<para>
- Use these annotations to specify methods those to be executed
+ Use these annotations to specify those methods to be executed
on a successful or failed execution, respectively, of that
<systemitem>pipeline</systemitem> in which the action
is configured:
@@ -1298,7 +1297,7 @@
these capabilities (for both gateway and ESB nodes), via the
<systemitem>filter mechanism</systemitem>.
</para>
-
+<!--
<note>
<para>
Please be aware that the name of the filter property, the
@@ -1307,7 +1306,7 @@
those that were present in earlier milestone releases.
</para>
</note>
-
+-->
<para>
The
<classname>org.jboss.soa.esb.filter.InputOutputFilter</classname>
@@ -1422,7 +1421,7 @@
the Enterprise Service Bus (in other words, the time it was
received.)</para></listitem>
</varlistentry>
-
+ <!--
<varlistentry>
<term><classname>org.jboss.soa.esb.gateway.original.file.name</classname></term>
<listitem><para>If the message was received via a
@@ -1430,7 +1429,7 @@
name of the original file from which the message was
sourced.</para></listitem>
</varlistentry>
-
+ -->
<varlistentry>
<term><classname>org.jboss.soa.esb.gatway.original.queue.name</classname></term>
<listitem><para>If the message was received via a Java Message Service
@@ -1565,7 +1564,7 @@
<title>
The "ServiceInvoker"
</title>
-
+ <!--
<para>
From a client's perspective, the Courier interface and its
various implementations can be used to interact with
@@ -1577,7 +1576,7 @@
the application. See the "Advanced" chapter for more details
on fail-over functionality.
</para>
-
+ -->
<para>
The <interfacename>ServiceInvoker</interfacename> was introduced in
<application>JBoss Enterprise Service Bus 4.2</application> to help simplify the
@@ -1615,7 +1614,7 @@
<exceptionname>ResponseTimeoutException</exceptionname> is
thrown.
</para>
-
+<!--
<note>
<para>
From <application>JBossESB 4.5</application> onwards, the
@@ -1624,7 +1623,7 @@
<exceptionname>MessageDeliverException</exceptionname>.
</para>
</note>
-
+-->
<para>
A
<exceptionname>RegistryException</exceptionname> is thrown from
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Configuration.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Configuration.xml 2011-01-11 00:14:47 UTC (rev 36514)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Configuration.xml 2011-01-11 00:25:55 UTC (rev 36515)
@@ -164,11 +164,11 @@
</figure>
<para>
- The <services> part of the configuration defines each of
- the Services under the management of this instance of the
- Enterprise Service Bus. It defines them as a series of
- <service> configurations. A <service> can also be
- decorated with the following attributes.
+ The <code><services></code> part of the configuration defines each of
+ the Services under the management of this instance of the Enterprise Service Bus.
+ It defines them as a series of <code><service></code> configurations. A
+ <code><service></code> can also be decorated with the following
+ attributes.
</para>
<table id="SOA_ESB_Programmers_Guide-Services-Service_Attributes">
@@ -570,111 +570,131 @@
<para>
So the transport specific implementations that are in place in
- this release are:
+ this release are: JMS, SQL, FTP, Hibernate, File System, Schedule, and
+ JMS/JCA Integration.
</para>
- <orderedlist>
- <listitem>
- <para> JMS:
- <jms-provider>,
- <jms-bus>,
- <jms-listener> and
- <jms-message-filter>: The
- <jms-message-filter> can be added
- to either the <jms-bus> or
- <jms-listener> elements. Where the
- <jms-provider> and
- <jms-bus> specify the JMS
- connection properties, the
- <jms-message-filter> specifies the
- actual message QUEUE/TOPIC and selector details.
- </para>
- </listitem>
+ <variablelist>
+ <varlistentry>
+ <term>JMS</term>
+ <listitem>
+ <para>
+ <code><jms-provider></code>,
+ <code><jms-bus></code>,
+ <code><jms-listener></code> and
+ <code><jms-message-filter></code>
+ </para>
+ <para>
+ The <jms-message-filter> can be added to either the <jms-bus>
+ or <jms-listener> elements. Where the <jms-provider> and
+ <jms-bus> specify the JMS connection properties, the
+ <jms-message-filter> specifies the actual message QUEUE/TOPIC and
+ selector details.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>SQL</term>
+ <listitem>
+ <para>
+ <code><sql-provider></code>,
+ <code><sql-bus></code>,
+ <code><sql-listener></code> and
+ <code><sql-message-filter></code>
+ </para>
+ <para>
+ The <sql-message-filter> can be added to either the <sql-bus>
+ or <sql-listener> elements. Where the <sql-provider> and
+ <sql-bus> specify the JDBC connection properties, the
+ <sql-message-filter> specifies the message/row selection and
+ processing properties.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>FTP</term>
+ <listitem>
+ <para>
+ <code><ftp-provider></code>,
+ <code><ftp-bus></code>,
+ <code><ftp-listener></code> and
+ <code><ftp-message-filter></code>
+ </para>
+ <para>
+ The <ftp-message-filter> can be added to either the <ftp-bus>
+ or <ftp-listener> elements. Where the <ftp-provider> and
+ <ftp-bus> specify the FTP access properties, the
+ <ftp-message-filter> specifies the message/file selection and
+ processing properties
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Hibernate</term>
+ <listitem>
+ <para>
+ <code><hibernate-provider></code>,
+ <code><hibernate-bus></code>,
+ <code><hibernate-listener></code>
+ </para>
+ <para>
+ The <hibernate-message-filter> can be added to either the
+ <hibernate-bus> or <hibernate-listener> elements. Where the
+ <hibernate-provider> specifies file system access properties like
+ the location of the hibernate configuration property, the
+ <hibernate-message-filter> specifies what classnames and events
+ should be listened to.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>File system</term>
+ <listitem>
+ <para>
+ <code><fs-provider></code>,
+ <code><fs-bus></code>,
+ <code><fs-listener></code> and
+ <code><fs-message-filter></code>
+ </para>
+ <para>
+ The <fs-message-filter> can be added to either the <fs-bus>
+ or <fs-listener> elements. Where the <fs-provider> and
+ <fs-bus> specify the File System access properties, the
+ <fs-message-filter> specifies the message/file selection and
+ processing properties.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>schedule</term>
+ <listitem>
+ <para>
+ <code><schedule-provider></code>
+ </para>
+ <para>
+ This is a special type of provider and differs from the bus based
+ providers listed above. See Scheduling for more information.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>JMS/JCA Integration</term>
+ <listitem>
+ <para>
+ <code><jms-jca-provider></code>
+ </para>
+ <para>
+ This provider can be used in
+ place of the <jms-provider> to enable delivery of incoming messages
+ using JCA inflow. This introduces a transacted flow to the action pipeline,
+ and thereby encompasses actions within a JTA transaction.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ </variablelist>
- <listitem>
- <para> SQL:
- <sql-provider>,
- <sql-bus>,
- <sql-listener> and
- <sql-message-filter>: The
- <sql-message-filter> can be added
- to either the <sql-bus> or
- <sql-listener> elements. Where the
- <sql-provider> and
- <sql-bus> specify the JDBC
- connection properties, the
- <sql-message-filter> specifies the
- message/row selection and processing properties.
- </para>
- </listitem>
-
- <listitem>
- <para>
- FTP:
- <ftp-provider>,
- <ftp-bus>,
- <ftp-listener> and
- <ftp-message-filter>: The
- <ftp-message-filter> can be added
- to either the <ftp-bus> or
- <ftp-listener> elements. Where the
- <ftp-provider> and
- <ftp-bus> specify the FTP access
- properties, the
- <ftp-message-filter> specifies the
- message/file selection and processing properties
- </para>
- </listitem>
- <listitem>
- <para>Hibernate:
- <hibernate-provider>, <hibernate-bus>,
- <hibernate-listener> : The
- <hibernate-message-filter> can be added to either the
- <hibernate-bus> or <hibernate-listener>
- elements. Where the <hibernate-provider> specifies
- file system access properties like the location of the
- hibernate configuration property, the
- <hibernate-message-filter> specifies what classnames
- and events should be listened to.
- </para>
- </listitem>
-
- <listitem>
- <para> File system:
- <fs-provider>,
- <fs-bus>,
- <fs-listener> and
- <fs-message-filter> The
- <fs-message-filter> can be added to
- either the <fs-bus> or
- <fs-listener> elements. Where the
- <fs-provider> and
- <fs-bus> specify the File System
- access properties, the
- <fs-message-filter> specifies the
- message/file selection and processing properties.
- </para>
- </listitem>
-
- <listitem>
- <para> schedule:
- <schedule-provider>. This is a
- special type of provider and differs from the bus based
- providers listed above. See Scheduling for more.
- </para>
- </listitem>
-
- <listitem>
- <para>JMS/JCA Integration :
- <jms-jca-provider>: This provider can be used in
- place of the <jms-provider> to enable delivery of
- incoming messages using JCA inflow. This introduces a
- transacted flow to the action pipeline, and thereby
- encompasses actions within a JTA transaction.
- </para>
- </listitem>
- </orderedlist>
<para>
As you'll notice, all of the currently implemented transport
@@ -813,7 +833,7 @@
<table>
<title>JMS Listener configuration</title>
<tgroup align="left" cols="3" colsep="1" rowsep="1">
- <colspec colname="c1" colwidth="1*"/>
+ <colspec colname="c1" colwidth="6*"/>
<colspec colname="c2" colwidth="4*"/>
<colspec colname="c3" colwidth="1*"/>
@@ -1192,16 +1212,15 @@
</row>
<row>
- <entry>remoteFileSystemStrategy-class</entry>
- <entry>Override the remote file system strategy
- with a class that implements:
- <classname>org.jboss.soa.esb.listeners.gateway.remotestrategies.RemoteFileSystemStrategy</classname>.
- Defaults to <classname>org.jboss.soa.esb.listeners.gateway.remotestrategies.ReadOnlyRemoteFileSystemStrategy</classname>
+ <entry>remoteFilesystemStrategy-class</entry>
+ <entry>Override the remote file system strategy with a class that
+ implements: <classname>org.jboss.soa.esb.listeners.gateway.remotestrategies.RemoteFileSystemStrategy</classname>.
+ Defaults to <classname>org.jboss.soa.esb.listeners.gateway.remotestrategies.ReadOnlyRemoteFileSystemStrategy</classname>
</entry>
</row>
<row>
- <entry>remoteFileSystemStrategy-configFile</entry>
+ <entry>remoteFilesystemStrategy-configFile</entry>
<entry>Specify a JBoss TreeCache configuration file on the local file
system or one that exists on the classpath. Defaults to looking for a
file named <filename>/ftpfile-cache-config.xml</filename> which it
@@ -1209,11 +1228,9 @@
</row>
<row>
- <entry>remoteFileSystemStrategy-cacheListener</entry>
- <entry>Specifies an JBoss
- <classname>TreeCacheListener</classname>
- implementation to be used with the
- TreeCache. Default is no TreeCacheListener.</entry>
+ <entry>removeFilesystemStrategy-cacheListener</entry>
+ <entry>Specifies an JBoss <classname>TreeCacheListener</classname> implementation
+ to be used with the TreeCache. Default is no TreeCacheListener.</entry>
</row>
<row>
@@ -1254,7 +1271,7 @@
<table>
<title>Configuration</title>
<tgroup align="left" cols="3" colsep="1" rowsep="1">
- <colspec colname="c1" colwidth="2*"/>
+ <colspec colname="c1" colwidth="6*"/>
<colspec colname="c2" colwidth="6*"/>
<colspec colname="c3" colwidth="5*"/>
<thead>
@@ -1308,12 +1325,12 @@
</title>
<para>
- Is a gateway implementation for receiving ESB unaware messages
- sent using the UDP protocol. The payload will be passed along
- to the action chain in the default ESB Message object location.
- Actions can call esbMessage.getBody().get() to retrieve the
- byte array payload from within their actions.
- </para>
+ The <literal>UDP Gateway</literal> is an implementation for receiving
+ ESB-unaware messages sent
+ via the <literal>UDP</literal> protocol. The payload will be passed along to the
+ action chain in the default ESB Message object location. Actions can
+ call <classname>esbMessage.getBody().get()</classname> to retrieve the byte array payload.
+ </para>
<table orient="land" id="UDP_Gateway_Configuration_table">
@@ -1735,7 +1752,7 @@
<row>
<entry>queryString</entry>
- <entry>Query String (See Servlet Spec)</entry>
+ <entry>Query String</entry>
</row>
<row>
@@ -1743,7 +1760,7 @@
<entry>The part of this request URL from the
protocol name up to the query string. The
web container does not decode this String.
- (See Servlet Spec)</entry>
+ </entry>
</row>
<row>
@@ -1753,8 +1770,7 @@
path information or a query string. Same as
the value of the CGI variable SCRIPT_NAME.
This method will return just "http") if the
- urlPattern was "/*". (See Servlet
- Spec)</entry>
+ urlPattern was "/*". </entry>
</row>
<row>
@@ -1876,7 +1892,7 @@
<para>
Asynchronous behavior is configured by adding an
- <asyncResponse> element to the <http-gateway>, as
+ <asyncHttpResponse> element to the <http-gateway>, as
follows:
</para>
@@ -1892,7 +1908,7 @@
<para>
The asynchronous response HTTP status code can be configured (away
from the default of 200) by simply setting the "statusCode"
- attribute on the <asyncResponse> element:
+ attribute on the <asyncHttpResponse> element:
</para>
<programlisting language="Java" role="JAVA"><xi:include href="extras/configuration/asynchronous2.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
@@ -1900,7 +1916,7 @@
<para>
As stated above, a zero length payload is returned (by default) for
asynchronous responses. This can be overridden by specifying a
- <payload> element on the <asyncResponse> element:
+ <payload> element on the <asyncHttpResponse> element:
</para>
<programlisting language="Java" role="JAVA"><xi:include href="extras/configuration/asynchronous3.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
@@ -2195,7 +2211,7 @@
</listitem>
<listitem>
<para>
- Refence the <http-bus> from the <http-gateway>
+ Refence the <http-bus> from the <http-listener>
using the "busrefid" attribute.
</para>
</listitem>
@@ -2359,49 +2375,68 @@
Camel Gateway
</title>
+ <warning>
<para>
- As it's name suggests, this gateway allows you to expose
- Message-Unaware Camel endpoints on JBossESB. This gateway
- leverages Apache Camel's input capabilities, translates the
- Camel Message to an ESB Message, and invokes the associated ESB
- Service.
+ The Camel Gateway is provided as a Technology Preview only.
+ Technology Preview features are not fully supported and may not be
+ functionally complete. They are not intended for production use.
+ These features are included to provide customers with early access
+ to upcoming product innovations, enabling them to test
+ functionality and provide feedback during the development process.
</para>
+
+ <para>
+ Red Hat JBoss support will provide commercially-reasonable efforts
+ to resolve any reported issues that customers experience when using
+ these features.
+ </para>
+ </warning>
+
+
+ <para>
+ As its name suggests, the Camel Gateway allows one to expose
+ message-unaware <firstterm>Camel</firstterm> end-points. It
+ leverages Apache Camel's input capabilities, translates
+ Camel messages to ESB messages and invokes the associated ESB
+ service.
+ </para>
<para>
- The most apparent difference betweeen the CamelGateway and the
- other Gateways provided within JBossESB is that the
- CamelGateway is not specific to any one type of transport. This
- is because we want to leverage all the different transports
- that Camel supports, so the role of the CamelGateway is really
- all about integration. To see all the different transports
- Camel can handle, please visit the Camel Component list here:
- <ulink url="http://camel.apache.org/components.html" />
+ The most apparent difference betweeen the Camel Gateway and the
+ other Gateways provided within the JBoss Enterprise Service Bus
+ is that the Camel Gateway is not tied to any one type of
+ transport. It has been designed to leverage all the different
+ transports that Camel supports, hence its roles is to provide a
+ high level of integration. To see all of the different
+ transports Camel can handle, please visit the Camel Component
+ list here: <ulink url="http://camel.apache.org/components.html"
+ />
</para>
<note>
<para>
Different Camel Components have different library dependencies.
- JBossESB only contains the camel-core.jar. You will have to add
- any other dependencies (including other camel-* jars or third
- party jars) you require.
+ The JBoss Enterprise Service Bus only contains the
+ <filename>camel-core.jar</filename>. One will have to manually
+ add any other dependencies required (including other camel-*
+ JARs and third party JARs).
</para>
</note>
<para>
Within the <providers> section of JBoss ESB, a new
- <camel-provider> section is available if you declare the
- use of the updated schema (jbossesb-1.3.0.xsd) in your
- jboss-esb.xml file.
+ <camel-provider> section becomes available if one declares the
+ use of the updated schema (jbossesb-1.3.0.xsd) in the
+ <filename>jboss-esb.xml</filename> file:
</para>
<programlisting language="Java" role="JAVA"><xi:include href="extras/configuration/camel1.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
<para>
- What is contained within the <camel-bus> element is the
- most interesting part, where you can have an unbounded number of
- <from uri=""/> elements. Those familiar with Camel XML
+ The most interesting part is that which is contained within the <camel-bus> element. An unbounded number of
+ <from uri=""/> elements can be added here. Those familiar with the Camel XML
configuration should be very comfortable with that element, as
- it does exactly what it does in native Camel XML configuration.
+ it does exactly what it does in the native Camel XML configuration.
There is also a new <camel-gateway> element, which can
reference the aforementioned bus via the busidref attribute:
</para>
@@ -2409,8 +2444,8 @@
<programlisting language="Java" role="JAVA"><xi:include href="extras/configuration/camel2.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
<para>
- You can also define <from uri=""/> elements under the
- <camel-gateway> element, without requiring a
+ It is possible to define <from uri=""/> elements under the
+ <camel-gateway> element, without using a
<camel-provider> at all:
</para>
@@ -2418,21 +2453,18 @@
<para>
There is also a short-hand mechanism, where you can specify one
- Camel “from” URI as an XML attribute at either the gateway
- level:
+ Camel "from" URI as an XML attribute at either the gateway
+ level or at the bus level::
</para>
<programlisting language="Java" role="JAVA"><xi:include href="extras/configuration/camel4.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
- <para>
- or at the bus level:
- </para>
<programlisting language="Java" role="JAVA"><xi:include href="extras/configuration/camel5.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
<note>
<para>
- It is important to understand that all Camel “from” URIs
+ It is important to understand that all Camel "from" URIs
defined at both the <camel-bus> and <camel-gateway>
level are cumulative, whether you use the element form and/or
the short-hand form.
@@ -2442,7 +2474,7 @@
<para>
At this point, you might wonder where the <to uri=””/>
elements are, because in Camel, you need to define at least one
- destination. In JBossESB, every Camel “from” URI translates to
+ destination. In the JBoss Enterprise Service Bus, every Camel "from" URI translates to
one route (added to all other routes in that gateway+bus), with
an implicit Camel “to” URI which invokes the associated Service
where you are assigning the <camel-gateway>.
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/JBossESB.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/JBossESB.xml 2011-01-11 00:14:47 UTC (rev 36514)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/JBossESB.xml 2011-01-11 00:25:55 UTC (rev 36515)
@@ -86,10 +86,10 @@
</para>
</listitem>
</itemizedlist>
-
+<!--
<para>
- To date, Rosetta has been used in mission critical deployments
- using Oracle Financials. The multi platform environment included an
+ To date, Rosetta has been used in various mission-critical deployments
+ using Oracle Financials. The multi-platform environment included an
IBM mainframe running z/OS, DB2 and Oracle databases hosted in the
mainframe and in smaller servers, with additional Windows and Linux
servers and a myriad of third party applications that offered
@@ -115,6 +115,7 @@
for the toolset), and to trigger their own ‘action classes’ that
can be unaware of transport and triggering mechanisms.
</para>
+-->
<important>
<para>
@@ -190,7 +191,15 @@
facilitated via a range of different approaches, including JMS,
flat-file systems and e. mail.
</para>
-
+
+ <para>
+ JBoss SOA Platform 5.1 includes JBoss Enterprise Data Services (based on Teiid). EDS is exposed as a JDBC driver or webservice, so that ESB services can consume them in that form. Note that the JDBS connection string for a EDS Virtual Database (VDB) differs some what from typical JDBC connection string. The correct format for a JBDC connection string for a VDB takes this form: <literal>jdbc:teiid:vdb_name at mm://localhost:31000</literal>.
+</para>
+
+<para>
+For details, refer to the <emphasis>EDS Developer Guide</emphasis>.
+ </para>
+
<para>
Here is a depiction of a typical <application>JBoss Enterprise
Service Bus</application> deployment:
@@ -207,8 +216,9 @@
<note>
<para>
Some of the components in the diagram (such as the lightweight
- directory access protocol server) are configuration choices and
- may not be provided "out-of-the-box." Furthermore, the distinction
+ directory access protocol server) are configuration choices.
+ Therefore, they are not be provided "out-of-the-box." Furthermore,
+ the distinction
shown between processors and actions is merely an illustrative
convenience intended to show the concepts involved when an
incoming event (that is, a message) triggers the underlying
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Legal_Notice.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Legal_Notice.xml 2011-01-11 00:14:47 UTC (rev 36514)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Legal_Notice.xml 2011-01-11 00:25:55 UTC (rev 36515)
@@ -13,12 +13,32 @@
License, Version 2. A copy of this license is included in <xref linkend="gpl" />.
</para>
+ <!-- Creative Commons
+ Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at <ulink
+ url="http://creativecommons.org/licenses/by-sa/3.0/" />. The original authors of this document, and Red Hat,
+ designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA,
+ if you distribute this document or an adaptation of it, you must provide the URL for the original version. -->
+
+ <!--
<para>
+ Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section
+ 4d of CC-BY-SA to the fullest extent permitted by applicable law.
+ </para>
+ -->
+
+ <para>
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and
RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
</para>
+ <!--
<para>
+ For guidelines on the permitted uses of the Fedora trademarks, refer to
+ <ulink url="https://fedoraproject.org/wiki/Legal:Trademark_guidelines" />.
+ </para>
+ -->
+
+ <para>
<trademark class="registered">Linux</trademark> is the registered trademark of Linus Torvalds in the United
States and other countries.
</para>
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Other_Components.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Other_Components.xml 2011-01-11 00:14:47 UTC (rev 36514)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Other_Components.xml 2011-01-11 00:25:55 UTC (rev 36515)
@@ -124,7 +124,7 @@
Use the <firstterm>content-based routing</firstterm> mechanism
to route messages based on arbitrarily complex rules. (These
rules can be defined in XPath, Regex Content-Based Routing
- (CBR) or JBoss Rules notation.)
+ (CBR) or JBoss Rules notation.) Alternatively, Smooks can provide content-based routing functionality.
</para>
</section>
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Revision_History.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Revision_History.xml 2011-01-11 00:14:47 UTC (rev 36514)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Revision_History.xml 2011-01-11 00:25:55 UTC (rev 36515)
@@ -7,30 +7,76 @@
<appendix id="appe-Publican-Revision_History">
<title>Revision History</title>
<simpara>
- <revhistory>
-
- <revision>
- <revnumber>1</revnumber>
- <date>Fri Jul 16 2010</date>
+ <revhistory>
+
+ <revision>
+ <revnumber>1.3-0</revnumber>
+ <date>Thu Jul 22 2010</date>
<author>
<firstname>David</firstname>
<surname>Le Sage</surname>
<email>dlesage at redhat.com</email>
- </author>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Major refactoring of book to synchronise with restructure of community documents</member>
+ <member>Section 4.1.4 Annotated Action Classes added</member>
+ <member>Section 9.10 Camel Gateway added</member>
+ <member>Updated for SOA 5.1</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+
+
+ <revision>
+ <revnumber>1.2</revnumber>
+ <date>Fri Jun 11 2010</date>
<author>
- <firstname>Darrin</firstname>
- <surname>Mison</surname>
- <email>dmison at redhat.com</email>
+ <firstname>David</firstname>
+ <surname>Le Sage</surname>
+ <email>dlesage at redhat.com</email>
</author>
+ <revdescription>
+ <simplelist>
+ <member>SOA-2072 - More detailed protocol examples. Section 11.7.7</member>
+ <member>Updated for SOA 5.0.2</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+
+
+ <revision>
+ <revnumber>1.1</revnumber>
+ <date>Tue Apr 20 2010</date>
+ <author>
+ <firstname>David</firstname>
+ <surname>Le Sage</surname>
+ <email>dlesage at redhat.com</email>
+ </author>
<revdescription>
<simplelist>
- <member>Initial conversion from OpenOffice ODT files.</member>
+ <member>Updated for SOA 5.0.1</member>
</simplelist>
</revdescription>
</revision>
-
- </revhistory>
- </simpara>
+ <revision>
+ <revnumber>1.0</revnumber>
+ <date>Tue Feb 23 2010</date>
+ <author>
+ <firstname>David</firstname>
+ <surname>Le Sage</surname>
+ <email>dlesage at redhat.com</email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Created</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+
+
+
+ </revhistory>
+</simpara>
</appendix>
-
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Service_Orientated_Architecture_Overview.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Service_Orientated_Architecture_Overview.xml 2011-01-11 00:14:47 UTC (rev 36514)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Service_Orientated_Architecture_Overview.xml 2011-01-11 00:25:55 UTC (rev 36515)
@@ -50,14 +50,13 @@
different vendors, such as SAP and PeopleSoft. Some of these software
packages may be used to conduct business with other companies
(customers, suppliers, etc.) and therefore what the company would
- like to do is to take those existing systems and make them
- available to other companies, by exposing them as services. A
- service here is some software component with a stable, published
- interface that can be invoked by clients (other software
- components). So, requesting and executing services involves
- software components owned by one company talking to components
- owned by another company, i.e., business-to-business (B2B)
- transactions.
+ like to do is to take those existing systems and make them available
+ to other firms, by exposing them as services. A service here is
+ some software component with a stable, published interface that can
+ be invoked by "clients" ( which are other software components). So, requesting
+ and executing services involves software components owned by one
+ company talking to components owned by another company, in other words,
+ business-to-business (B2B) transactions.
</para>
<para>
@@ -103,10 +102,9 @@
providing standard interaction protocols (HTTP) and data formats
(XML) but, by themselves, these standards are not enough to support
application integration. They do not define interface definition
- languages, name and directory services, transaction protocols and
- so forth. It is the gap between that which the Web provides and
- what application integration requires that Web services are trying
- to fill.
+ languages, name and directory services, transaction protocols and so forth.
+ It is the gap between that which the Web provides and what application
+ integration requires that Web services are trying to fill.
</para>
<para>
@@ -128,17 +126,15 @@
</para>
<para>
- However, if you connect your inventory system to your accounting
- system with XML, it gets more interesting. Now, whenever you buy or
- sell something, the implications for your inventory and your cash
- flow can be tracked in one step. If you go further, and connect
- your warehouse management system, customer ordering system,
- supplier ordering systems, and your shipping company with XML,
- suddenly that inventory management system is worth a lot. You can
- do end-to-end management of your business while dealing with each
- transaction only once, instead of once for every system it affects.
- A lot less work and a lot less opportunity for errors. These
- connections can be made easily using Web services.
+ However, if you connect your inventory system to your accounting software with
+ XML, it becomes more interesting. Now, whenever you buy or sell something, the
+ implications for your inventory and your cash flow can be tracked in one step. If
+ you go further, and connect your warehouse management system, customer ordering
+ system, supplier ordering systems, and your shipping company with XML, suddenly
+ that inventory management system is worth a lot. You can do end-to-end management
+ of your business while dealing with each transaction only once, instead of over and over
+ for every system it affects. This results in a lot less work and opportunities for errors.
+ These connections can be made easily using Web services.
</para>
<para>
@@ -608,7 +604,7 @@
</section>
</section>
-
+ <!-- REMOVED
<section>
<title>JBossESB and its Relationship with SOA</title>
@@ -629,5 +625,5 @@
low-level API and patterns.
</para>
</section>
-
+ -->
</appendix>
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Services_and_Messages.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Services_and_Messages.xml 2011-01-11 00:14:47 UTC (rev 36514)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/Services_and_Messages.xml 2011-01-11 00:25:55 UTC (rev 36515)
@@ -212,7 +212,7 @@
<para>
Every interaction between clients and services occurs through
the exchange of messages. Therefore, Red Hat recommends making
- use of a <firstterm>message-exchange pattern</firstterm> during
+ use of a <firstterm>message-exchange pattern</firstterm> (MEP) during
the development process, the reason being that this will
encourage <firstterm>loose coupling</firstterm>. Requests and
responses should be independent messages, correlated where
@@ -323,21 +323,12 @@
<warning>
<para>
- Do not use either <interfacename>Properties</interfacename> or
- <interfacename>Attachments</interfacename> at this time.
- </para>
-
- <para>
- The general concepts that they embody are under
- re-evaluation and may change significantly in future
- releases.
+ In JBossESB, Attachments and Properties are not treated
+ differently from the Body. The general concepts they
+ embody are currently being re-evaluated and may change
+ significantly in future releases. As such, we recommend
+ developers do not use Attachments.
</para>
-
- <para>
- Put <interfacename>Property</interfacename> and
- <interfacename>Attachment</interfacename> data in the
- message body instead.
- </para>
</warning>
@@ -365,16 +356,14 @@
contexts. <firstterm>User-enhanced contexts</firstterm> are
also supported.
</para>
-
+
<note>
<para>
- The 4.x release of JBossESB does not support
- user-enhanced Contexts. This will be a feature of the
- 5.0 release.
+ Version 5.0 of the JBoss Enterprise Service Bus will be the first to support user-enhanced contexts.
</para>
</note>
- <para>
+ <para>
The <firstterm>body</firstterm> contains the message's
"payload". Use the body to send any number of differing
data types. (One is not restricted to just sending and
@@ -397,14 +386,12 @@
<programlisting language="Java" role="JAVA"><xi:include href="extras/services_and_messages/public_interface.java" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
-
+<!-- REPETITIVE
<para>
- A Body can be used to convey arbitrary information types and
- arbitrary numbers of each type, i.e., it is not necessary to
- restrict yourself to sending and receiving single data items
- within a Body.
+ The body can be used to convey any number of
+ each type. In other words, one is not restricted to just sending and receiving single data items.
</para>
-
+-->
<important>
<para>
The message body's <firstterm>byte array</firstterm> component
@@ -440,21 +427,8 @@
<warning>
<para>
- Do not use either <interfacename>Properties</interfacename> or
- <interfacename>Attachments</interfacename> at this time.
- </para>
-
- <para>
- The general concepts that they embody are under
- re-evaluation and may change significantly in future
- releases.
+ In JBossESB, Attachments and Properties are not treated differently from the Body. The general concepts they embody are currently being re-evaluated and may change significantly in future releases. As such, we recommend developers do not use Attachments.
</para>
-
- <para>
- Put <interfacename>Property</interfacename> and
- <interfacename>Attachment</interfacename> data in the
- message body instead.
- </para>
</warning>
@@ -486,10 +460,7 @@
body. Such attachments include images, drawings, documents in binary
formats and compressed files. The
<interfacename>Attachment</interfacename> interface supports
- both named and unnamed attachments. However, note that, in the
- current release, only Java
- serialized objects can be attached. (This restriction will be
- removed in a subsequent release.)
+ both named and unnamed attachments.
</para>
@@ -519,9 +490,8 @@
<para>
- Readers sometimes find themselves overwhelmed when they find
- that they have to choose between attachments, properties and
- named objects when deciding where to put the payload. However,
+ Users may find themselves overwhelmed when they have to choose between
+attachments, properties and named objects when deciding where to put the payload. However,
the choice is really quite straightforward:
</para>
@@ -762,15 +732,7 @@
methods of the interface that created it.
</para>
- <para>
- The <classname>XMLMessageFactory</classname> and
- <classname>SerializedMessageFactory</classname> represent
- more convenient ways with which to work with messages than
- that offered by the <classname>MessageFactory</classname>
- and its associated classes. However, it is the latter which
- will now be described.
- </para>
-
+
<note>
<para>
These extensions to the base Body interface are provided in
@@ -816,7 +778,7 @@
<colspec colname="c1" colwidth="1*"/>
<colspec colname="c2" colwidth="1*"/>
<colspec colname="c3" colwidth="1*"/>
- <colspec colname="c4" colwidth="5*"/>
+ <colspec colname="c4" colwidth="8*"/>
<thead>
<row>
<entry>Property</entry><entry>Type</entry><entry>Required?</entry><entry>Description</entry>
@@ -1062,21 +1024,8 @@
<warning>
<para>
- Do not use either <interfacename>Properties</interfacename> or
- <interfacename>Attachments</interfacename> at this time.
- </para>
-
- <para>
- The general concepts that they embody are under
- re-evaluation and may change significantly in future
- releases.
+ In JBossESB, Attachments and Properties are not treated differently from the Body. The general concepts they embody are currently being re-evaluated and may change significantly in future releases. As such, we recommend developers do not use Attachments.
</para>
-
- <para>
- Put <interfacename>Property</interfacename> and
- <interfacename>Attachment</interfacename> data in the
- message body instead.
- </para>
</warning>
@@ -1155,10 +1104,9 @@
<para>
Although each Enterprise Service Bus component treats every
message as a collection of Java objects, it is often
- necessary to serialize these messages. Situations in which
- one might have to do so include when the data is to be
+ necessary to serialize these messages. Do so when the data is to be
stored, when the message is to be sent between different
- ESB processes and when one is debugging.
+ ESB processes and when debugging.
</para>
@@ -1258,12 +1206,9 @@
</title>
<para>
- As mentioned previously, the <application>JBoss
- Enterprise Service Bus</application> supports two
- serialized message formats:
- <literal>MessageType.JBOSS_XML</literal> and
- <literal>MessageType.JAVA_SERIALIZED</literal>. Read
- this section to learn more about each of these.
+ There are two serialized message formats, JBOSS_XML and
+ JBOSS_SERIALIZED. Read this
+ section to learn about them.
</para>
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/building_and_using_services/Code_Example6.xmlt
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/building_and_using_services/Code_Example6.xmlt 2011-01-11 00:14:47 UTC (rev 36514)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/building_and_using_services/Code_Example6.xmlt 2011-01-11 00:25:55 UTC (rev 36515)
@@ -45,5 +45,8 @@
</NotificationList>
</property>
- </action> </actions> </service> </services>
-</jbossesb>
\ No newline at end of file
+ </action>
+ </actions>
+ </service>
+ </services>
+</jbossesb>
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/building_and_using_services/annotate3.xmlt
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/building_and_using_services/annotate3.xmlt 2011-01-11 00:14:47 UTC (rev 36514)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/building_and_using_services/annotate3.xmlt 2011-01-11 00:25:55 UTC (rev 36515)
@@ -1,6 +1,6 @@
<service .....>
<actions>
<action name="logger" class="com.acme.actions.MyLogAction"
- process=”log” />
+ process="log" />
</actions>
</service>
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/building_and_using_services/annotate7.java
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/building_and_using_services/annotate7.java 2011-01-11 00:14:47 UTC (rev 36514)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/building_and_using_services/annotate7.java 2011-01-11 00:25:55 UTC (rev 36515)
@@ -2,9 +2,8 @@
@Process
public OrderAck storeOrder(
- @BodyParam("order-header") OrderHeader
- orderHeader,
- @BodyParam("order-items") OrderItems orderItems) {
+ @BodyParam("order-header") OrderHeader orderHeader,
+ @BodyParam("order-items") OrderItems orderItems) {
// process the order parameters and return an ack...
}
Added: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/invm/Code_Example7.xmlt
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/invm/Code_Example7.xmlt (rev 0)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/invm/Code_Example7.xmlt 2011-01-11 00:25:55 UTC (rev 36515)
@@ -0,0 +1,9 @@
+<service category="ServiceCat" name="ServiceName" invmScope="GLOBAL"
+ description="Test Service">
+ <actions mep="RequestResponse">
+ <action name="action"
+ class="org.jboss.soa.esb.listeners.SetPayloadAction">
+ <property name="payload" value="Tom Fennelly" />
+ </action>
+ </actions>
+</service>
\ No newline at end of file
Added: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/invm/Code_Example9.xmlt
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/invm/Code_Example9.xmlt (rev 0)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/invm/Code_Example9.xmlt 2011-01-11 00:25:55 UTC (rev 36515)
@@ -0,0 +1,9 @@
+<service category="ServiceCat" name="Service2"
+ description="Test Service">
+ <property name="inVMLockStep" value="true" />
+ <property name="inVMLockStepTimeout" value="4000" />
+
+ <actions mep="RequestResponse">
+ <action name="action" class="org.jboss.soa.esb.mock.MockAction" />
+ </actions>
+</service>
Added: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/invm/Code_example_invm_passbyvalue.xmlt
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/invm/Code_example_invm_passbyvalue.xmlt (rev 0)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/invm/Code_example_invm_passbyvalue.xmlt 2011-01-11 00:25:55 UTC (rev 36515)
@@ -0,0 +1,6 @@
+<service category="ServiceCat" name="Service2" description="Test Service">
+ <property name="inVMPassByValue" value="true" />
+ <actions mep="RequestResponse">
+ <action name="action" class="org.jboss.soa.esb.mock.MockAction" />
+ </actions>
+</service>
\ No newline at end of file
Added: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/invm/inVM_example1.xmlt
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/invm/inVM_example1.xmlt (rev 0)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/invm/inVM_example1.xmlt 2011-01-11 00:25:55 UTC (rev 36515)
@@ -0,0 +1,9 @@
+<service category="ServiceCat" name="ServiceName"
+ description="Test Service">
+ <actions mep="RequestResponse">
+ <action name="action"
+ class="org.jboss.soa.esb.listeners.SetPayloadAction">
+ <property name="payload" value="Tom Fennelly" />
+ </action>
+ </actions>
+</service>
\ No newline at end of file
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/services_and_messages/code1.xmlt
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/services_and_messages/code1.xmlt 2011-01-11 00:14:47 UTC (rev 36514)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Programmers_Guide/en-US/extras/services_and_messages/code1.xmlt 2011-01-11 00:25:55 UTC (rev 36515)
@@ -1,5 +1,5 @@
<?xml version = "1.0" encoding = "UTF-8"?>
-<jbossesb xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.0.1.xsd" invmScope=”GLOBAL”>
+<jbossesb xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.0.1.xsd" invmScope="GLOBAL">
<services>
<service category="Retail" name="ShoeStore" description="Acme Shoe Store Service">
More information about the jboss-svn-commits
mailing list