You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@servicemix.apache.org by fo...@apache.org on 2006/02/28 07:52:28 UTC
svn commit: r381583 [1/2] - /incubator/servicemix/site/
Author: foconer
Date: Mon Feb 27 22:52:24 2006
New Revision: 381583
URL: http://svn.apache.org/viewcvs?rev=381583&view=rev
Log:
Latest HTML dump from the confluence wiki created by wikimesh; see the confluence log for a detailed changelog
Modified:
incubator/servicemix/site/Ant+Tasks
incubator/servicemix/site/Articles
incubator/servicemix/site/Basic
incubator/servicemix/site/Client+API
incubator/servicemix/site/Container+MBean
incubator/servicemix/site/Glossary
incubator/servicemix/site/Home
incubator/servicemix/site/How+does+ServiceMix+compare+to+Celtix
incubator/servicemix/site/How+does+ServiceMix+compare+to+Mule
incubator/servicemix/site/How+does+ServiceMix+compare+to+Synapse
incubator/servicemix/site/I+can+not+create+a+JIRA+issue
incubator/servicemix/site/InstallComponentTask
incubator/servicemix/site/InstallSharedLibraryTask
incubator/servicemix/site/Management
incubator/servicemix/site/News
incubator/servicemix/site/POJO+support
incubator/servicemix/site/Publish+Subscribe+Routing
incubator/servicemix/site/Release+Guide
incubator/servicemix/site/Seda+Flow+MBean
incubator/servicemix/site/ShutDownAssemblyTask
incubator/servicemix/site/ShutDownComponentTask
incubator/servicemix/site/StartAssemblyTask
incubator/servicemix/site/StartComponentTask
incubator/servicemix/site/StopAssemblyTask
incubator/servicemix/site/StopComponentTask
incubator/servicemix/site/Team
incubator/servicemix/site/UninstallAssemblyTask
incubator/servicemix/site/UninstallComponentTask
incubator/servicemix/site/UninstallSharedLibraryTask
incubator/servicemix/site/WAR+Deployment
incubator/servicemix/site/WSIF
incubator/servicemix/site/file+binding
incubator/servicemix/site/index.html
Modified: incubator/servicemix/site/Ant+Tasks
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/Ant%2BTasks?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/Ant+Tasks (original)
+++ incubator/servicemix/site/Ant+Tasks Mon Feb 27 22:52:24 2006
@@ -216,7 +216,7 @@
<div id="Content">
<p>A requirement of the JBI/JSR208 is to allow the remote installation, deployment and management of Components. A prefered way of doing this is by Ant Tasks, that use the JMX interfaces exposed by the management of the Container.</p>
<h2><a name="AntTasks-JbiTask"></a>JbiTask</h2>
- <p>All ServiceMix Ant Tasks are derived from JbiTask - see <span class="nobr"><a href="http://servicemix.codehaus.org/maven/apidocs/org/servicemix/jbi/management/task/JbiTask.html" rel="nofollow">JbiTask </a></span> and share it'sattributes: <br clear="all">
+ <p>All ServiceMix Ant Tasks are derived from JbiTask - see <span class="nobr"><a href="http://servicemix.org/maven/servicemix-core/apidocs/org/apache/servicemix/jbi/management/task/JbiTask.html" rel="nofollow">JbiTask</a></span> and share it's attributes: <br clear="all">
</p>
<p class="paragraph">
<table align="center" border=0 cellpadding=5 cellspacing="8px" class="infoMacro" width="85%">
@@ -232,12 +232,12 @@
<tr>
<th class="confluenceTh"> Name </th>
<th class="confluenceTh"> type </th>
- <th class="confluenceTh">Description </th>
+ <th class="confluenceTh"> Description </th>
</tr>
<tr>
<td class="confluenceTd"> serverProtocol </td>
<td class="confluenceTd"> String </td>
- <td class="confluenceTd"> the default protcol used for connecting with the ServiceMix JMX MBeanServer (default is <b>rmi</b>)</td>
+ <td class="confluenceTd"> the default protcol used for connecting with the ServiceMix JMX MBeanServer (default is <b>rmi</b>) </td>
</tr>
<tr>
<td class="confluenceTd"> namingHost </td>
@@ -247,7 +247,7 @@
<tr>
<td class="confluenceTd"> containerName </td>
<td class="confluenceTd"> String </td>
- <td class="confluenceTd"> name of the ServiceMix JBI Container to connect to (default is <b>defaultJBI</b>)</td>
+ <td class="confluenceTd"> name of the ServiceMix JBI Container to connect to (default is <b>defaultJBI</b>) </td>
</tr>
<tr>
<td class="confluenceTd"> jmxDomainName </td>
@@ -280,7 +280,8 @@
</tr>
</table>
</p>
- <p>AntTasks derived from JbiTask include:</p>
+ <br>
+ <p class="paragraph"> AntTasks derived from JbiTask include: </p>
<ul>
<li><a href="AssemblyDescriptorTask" title="AssemblyDescriptorTask">AssemblyDescriptorTask</a></li>
<li><a href="DeployedAssembiliesTask" title="DeployedAssembiliesTask">DeployedAssembiliesTask</a></li>
Modified: incubator/servicemix/site/Articles
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/Articles?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/Articles (original)
+++ incubator/servicemix/site/Articles Mon Feb 27 22:52:24 2006
@@ -216,6 +216,7 @@
<div id="Content">
<h2><a name="Articles-Articles"></a>Articles</h2>
<ul>
+ <li><span class="nobr"><a href="http://www.fiveclouds.com/articles/2006/02/11/servicemix-deployments-in-eclipse" rel="nofollow">Great article</a></span> by Philip Dodds showing ServiceMix deployments being created in Eclipse</li>
<li><span class="nobr"><a href="http://www.zapthink.com/report.html?id=ZAPFLASH-10272004" rel="nofollow">SOA Governance: Reengineering IT Governance</a></span> By Jason Bloomberg</li>
<li><span class="nobr"><a href="http://www.theserverside.com/articles/article.tss?l=JBIforSOA" rel="nofollow">JBI - A Standard-based approach for SOA</a></span> by Meeraj Kinnumpurath</li>
<li><span class="nobr"><a href="http://www.javaworld.com/javaworld/jw-12-2005/jw-1212-esb.html" rel="nofollow">ServiceMix as an enterprise service bus</a></span> by J. Jeffrey Hanson</li>
@@ -223,10 +224,13 @@
<li><span class="nobr"><a href="http://java.sys-con.com/read/117740.htm" rel="nofollow">SOA + EDA = ServiceMix</a></span></li>
<li><span class="nobr"><a href="http://java.sun.com/integration/" rel="nofollow">Sun's JBI site</a></span></li>
<li><span class="nobr"><a href="https://wiki.objectweb.org/celtix/Wiki.jsp?page=Research" rel="nofollow">Celix's ESB links</a></span></li>
- <li>Steve Vinoski's <span class="nobr"><a href="http://dsonline.computer.org/portal/site/dsonline/menuitem.9ed3d9924aeb0dcd82ccc6716bbe36ec/index.jsp?&pName=dso_level1&path=dsonline/0507&file=w4tow.xml&xsl=article.xsl&" rel="nofollow">JBI article</a></span></li>
+ <li>Steve Vinoski's <span class="nobr"><a href="http://dsonline.computer.org/portal/site/dsonline/menuitem.9ed3d9924aeb0dcd82ccc6716bbe36ec/index.jsp?&amp;amp;pName=dso_level1&amp;amp;path=dsonline/0507&amp;amp;file=w4tow.xml&amp;amp;xsl=article.xsl&amp;amp;" rel="nofollow">JBI article</a></span></li>
<li>Frank Summer's <span class="nobr"><a href="http://www.artima.com/lejava/articles/jbi2.html" rel="nofollow">SOA JBI</a></span></li>
</ul>
- <h3><a name="Articles-JBINews%2Cblogsandforms"></a>JBI News, blogs and forms</h3>
+ <h3><a name="Articles-JBI%26ESBNews%2Cblogsandforms"></a>JBI & ESB News, blogs and forms</h3>
+ <ul>
+ <li><span class="nobr"><a href="http://www.computerworld.com/developmenttopics/development/webservices/story/0,10801,108478,00.html" rel="nofollow">What Is an ESB, and Do You Really Need One?</a></span> advice by Sandy Carter, IBM</li>
+ </ul>
<ul>
<li><span class="nobr"><a href="http://azur.typepad.com/bpel/2005/12/sca_jbi_and_mor.html" rel="nofollow">SCA, JBI and more..</a></span> which echos our <a href="How+does+ServiceMix+compare+to+Tuscany+or+SCA" title="How does ServiceMix compare to Tuscany or SCA">FAQ entry</a></li>
<li><span class="nobr"><a href="http://dx.doi.org/10.1571/PSGP7-14-05CC" rel="nofollow">Java Business Integration (JBI) Gains Industry Support</a></span> by Patricia Seybold Group</li>
Modified: incubator/servicemix/site/Basic
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/Basic?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/Basic (original)
+++ incubator/servicemix/site/Basic Mon Feb 27 22:52:24 2006
@@ -214,7 +214,7 @@
<div>
<div id="Content">
- <h3><a name="Basic-OverviewoftheServiceMix1.xBasicExample"></a>Overview of the ServiceMix 1.x <em>Basic</em> Example</h3>
+ <h3><a name="Basic-OverviewoftheServiceMixBasicExample"></a>Overview of the ServiceMix Basic Example</h3>
<p>This document describes how to run the <em>Basic</em> example and provides details about what it does. For information on the business use case, please refer to: <span class="nobr"><a href="http://www.servicemix.org/Use+Cases" rel="nofollow">Use Case for Basic</a></span>. <br clear="all">
<br clear="all"> The Basic example illustrates the following:</p>
<ul>
@@ -226,7 +226,7 @@
<li>how to use tracing</li>
</ul>
<p>The source code for the Basic example is located in the ServiceMix installation directory under the <tt>examples\basic</tt> directory in the <tt>servicemix.xml</tt> file. It is recommended that you refer to the source code while reading this document. <br clear="all">
- <br clear="all"> There are several components in the <tt>servicemix.xml</tt> file. One component sets off a trigger to send messages to a source destination. Then those messages are consumed by another component and sent to a different output destination. A trace component displays the messages as they arrive. <br clear="all">
+ <br clear="all"> There are several components in the <tt>servicemix.xml</tt>file. One component sets off a trigger to send messages to a source destination. Then those messages are consumed by another component and sent to a different output destination. A trace component displays the messages as they arrive. <br clear="all">
<br clear="all">
</p>
<h3><a name="Basic-RunningtheBasicExample"></a>Running the <em>Basic</em> Example</h3>
@@ -236,12 +236,14 @@
<div class="codeContent"><pre class="code-java">cd [servicemix_install_dir]\examples\basic</pre></div>
</div>
</p>
+ <p> </p>
<p>Then type:</p>
<p class="paragraph">
<div class="code">
<div class="codeContent"><pre class="code-java">[servicemix_install_dir]\bin\servicemix servicemix.xml</pre></div>
</div>
</p>
+ <p> </p>
<p>where <tt>servicemix_install_dir</tt> is the directory in which ServiceMix was installed. <br clear="all">
<br clear="all">
</p>
@@ -254,11 +256,12 @@
<tr>
<td valign="top"><img align="absmiddle" alt="" border=0 height=16 src="http://www.servicemix.org/images/icons/emoticons/check.gif" width=16></td>
<td><b class="strong">Handy Hint</b><br>
- <p>Add <em>$SERVICEMIX_HOME\bin</em> directory to <em>$PATH</em> variable to simplify execution of the example.</p>
- </td>
+ <br> Add <em>$SERVICEMIX_HOME\bin</em> directory to <em>$PATH</em> variable to simplify execution of the example.</td>
</tr>
</table>
</p>
+ <br>
+ <p class="paragraph"> </p>
<h3><a name="Basic-StoppingtheBasicExample"></a>Stopping the <em>Basic</em> Example</h3>
<p>To terminate the Basic example type "CTRL-C" in the command shell in which it is running and answer "y" to the "Terminate batch job (y/n)?" question. <br clear="all">
</p>
@@ -270,10 +273,12 @@
<div class="panel" style="border-style: solid; border-color: #ccc; ">
<div class="panelHeader" style="border-bottom-style: solid; border-bottom-color: #ccc; "><b>Basic Example Message Flow Diagram</b></div>
<div class="panelContent">
+ <p> </p>
<div align="center"><img border=0 src="http://www.servicemix.org/download/attachments/29640/basicflow1.jpg"></div>
- </div>
+ <br> </div>
</div>
</p>
+ <p> </p>
<p>
<br clear="all">
<br clear="all">
@@ -283,7 +288,7 @@
<ol>
<li>The <em>timer</em> component sends a message to <em>inputSender</em> through the Normalized Message Router (NMR).</li>
<li><em>inputSender</em> converts the message (marshals it) into a JMS message, then uses the <em>jmsTemplate</em> bean to publish the message.</li>
- <li><em>jmsTemplate</em> uses the <em>jmsFactory</em> bean to get a connection to the port associated with the JMS topic called "demo.org.servicemix.source." The message is published on the "demo.org.servicemix.source" topic.</li>
+ <li><em>jmsTemplate</em> uses the <em>jmsFactory</em>bean to get a connection to the port associated with the JMS topic called "demo.org.servicemix.source." The message is published on the "demo.org.servicemix.source" topic.</li>
<li><em>jencks</em> (the JCA resource adapter) listens on port 61616 for messages.</li>
<li><em>inputReceiver</em> subscribes to the "demo.org.servicemix.source" topic via <em>jencks</em> and receives the JMS message.</li>
<li><em>inputReceiver</em> normalizes the JMS message and sends it to <em>outputSender</em> via the NMR.</li>
@@ -300,21 +305,22 @@
</p>
<p class="paragraph">
<div class="code">
- <div class="codeContent"><pre class="code-java">[INFO] TraceComponent - -Exchange: org.servicemix.jbi.messaging.InOnlyImpl@4fdf11 received IN message:
-org.servicemix.jbi.messaging.NormalizedMessageImpl@1be0369{properties: {org.servicemix.jms.message=ACTIVEMQ_TEXT_MESSAGE:
-id = 0 ActiveMQMessage{ , jmsMessageID = <span class="code-keyword">null</span>, bodyAsBytes = org.activemq.io.util.ByteArray@1d1fc02,
+ <div class="codeContent"><pre class="code-java">[INFO] TraceComponent - -Exchange: org.servicemix.jbi.messaging.InOnlyImpl@4fdf11 received IN message:
+org.servicemix.jbi.messaging.NormalizedMessageImpl@1be0369{properties: {org.servicemix.jms.message=ACTIVEMQ_TEXT_MESSAGE:
+id = 0 ActiveMQMessage{ , jmsMessageID = <span class="code-keyword">null</span>, bodyAsBytes = org.activemq.io.util.ByteArray@1d1fc02,
readOnlyMessage = <span class="code-keyword">true</span>, jmsClientID = 'ID:Lisas-2828-1126207917359-23:0' ,
- jmsCorrelationID = '<span class="code-keyword">null</span>' , jmsDestination = demo.org.servicemix.result, jmsReplyTo = <span class="code-keyword">null</span>, jmsDeliveryMode = 2,
+ jmsCorrelationID = '<span class="code-keyword">null</span>' , jmsDestination = demo.org.servicemix.result, jmsReplyTo = <span class="code-keyword">null</span>, jmsDeliveryMode = 2,
jmsRedelivered = <span class="code-keyword">false</span>, jmsType = '<span class="code-keyword">null</span>' , jmsExpiration = 0, jmsPriority = 4, jmsTime
-stamp = 1126207938593, properties = {}, readOnlyProperties = <span class="code-keyword">true</span>, entryBrokerName = 'ID:Lisas-2828-1126207917359-0:0' ,
-entryClusterName = '<span class="code-keyword">default</span>' , consumerNos = [0], transactionId = '<span class="code-keyword">null</span>' , xaTransacted = <span class="code-keyword">false</span>,
-consumerIdentifer = 'ID:Lisas-2828-1126207917359-14:0' , messageConsumed = <span class="code-keyword">false</span>, transientConsumed = <span class="code-keyword">true</span>,
+stamp = 1126207938593, properties = {}, readOnlyProperties = <span class="code-keyword">true</span>, entryBrokerName = 'ID:Lisas-2828-1126207917359-0:0' ,
+entryClusterName = '<span class="code-keyword">default</span>' , consumerNos = [0], transactionId = '<span class="code-keyword">null</span>' , xaTransacted = <span class="code-keyword">false</span>,
+consumerIdentifer = 'ID:Lisas-2828-1126207917359-14:0' , messageConsumed = <span class="code-keyword">false</span>, transientConsumed = <span class="code-keyword">true</span>,
sequenceNumber = 7, deliveryCount = 1, dispatchedFromDLQ = <span class="code-keyword">false</span>, messageAcknowledge = org.activemq.ActiveMQSession@1de7497,
jmsMessageIdentity = <span class="code-keyword">null</span>, producerKey = ID:Lisas-2828-1126207917359-29: }, text = <?xml version=<span class="code-quote">"1.0"</span> encoding=<span class="code-quote">"UTF-8"</span>?>
<timer><name>My Example Job</name><group>ServiceMix</group><fullname>ServiceMix.My Example Job</fullname><description/><fireTime>
Thu Sep 08 12:32:18 PDT 2005</fireTime></timer>}}</pre></div>
</div>
</p>
+ <p> </p>
<h3><a name="Basic-Details"></a>Details</h3>
<p>The following table provides more details about the function of each component and bean in the servicemix.xml file. <br clear="all">
<br clear="all">
@@ -323,52 +329,52 @@
<table class="confluenceTable">
<tbody>
<tr>
- <th class="confluenceTh">Component or Bean ID</th>
- <th class="confluenceTh">Description</th>
+ <th class="confluenceTh"> Component or Bean ID </th>
+ <th class="confluenceTh"> Description </th>
</tr>
<tr>
<td class="confluenceTd"><em>jbi</em></td>
- <td class="confluenceTd"><em>jbi</em> is the "id" of the JBI container and provides the basic infrastructure services for the following components: <em>timer</em>, <em>inputSender</em>, <em>inputReceiver</em>, <em>outputSender</em>, <em>jmsTrace</em>, and <em>trace</em>. During initialization, several singletons are instantiated: <em>transactionManager</em>, <em>broker</em>, <em>jencks</em>, <em>jmsFactory</em>, and <em>jbi</em>. After initialization, the components in the <em>jbi</em> container are activated, starting with the <em>timer</em> component.</td>
+ <td class="confluenceTd"><em>jbi</em> is the "id" of the JBI container and provides the basic infrastructure services for the following components: <em>timer</em>, <em>inputSender</em>, <em>inputReceiver</em>, <em>outputSender</em>, <em>jmsTrace</em>, and <em>trace</em>. During initialization, several singletons are instantiated: <em>transactionManager</em>, <em>broker</em>, <em>jencks</em>, <em>jmsFactory</em>, and <em>jbi</em>. After initialization, the components in the <em>jbi</em> container are activated, starting with the <em>timer</em> component. </td>
</tr>
<tr>
<td class="confluenceTd"><em>timer</em></td>
- <td class="confluenceTd">The <em>timer</em> component shows the use of the QuartzComponent class. Every 5 seconds, until the program is terminated, the timer component kicks off an instance of a SimpleTrigger, which is associated with an instance of JobDetail. The job has a property called "name" with a value of "My Example Job" and another property called "group" with a value of "ServiceMix." The resulting message is converted to a normalized message and routed through the NMR. </td>
+ <td class="confluenceTd"> The <em>timer</em> component shows the use of the QuartzComponent class. Every 5 seconds, until the program is terminated, the timer component kicks off an instance of a SimpleTrigger, which is associated with an instance of JobDetail. The job has a property called "name" with a value of "My Example Job" and another property called "group" with a value of "ServiceMix." The resulting message is converted to a normalized message and routed through the NMR. </td>
</tr>
<tr>
<td class="confluenceTd"><em>inputSender</em></td>
- <td class="confluenceTd">This is a component inside the JBI container. It receives the normalized message (the message from the trigger), converts it to a JMS message, and publishes it to the topic called demo.org.servicemix.source. It uses the <em>jmsTemplate</em>(1) bean to handle the publish.</td>
+ <td class="confluenceTd"> This is a component inside the JBI container. It receives the normalized message (the message from the trigger), converts it to a JMS message, and publishes it to the topic called demo.org.servicemix.source. It uses the <em>jmsTemplate</em>(1) bean to handle the publish. </td>
</tr>
<tr>
<td class="confluenceTd"><em>inputReceiver</em></td>
- <td class="confluenceTd">This component uses <em>jencks</em> , the JCA container, to listen on port 61616 for a JMS message on the topic called "demo.org.servicemix.source." <em>inputReceiver</em> subscribes to the demo.org.servicemix.source topic. It takes the message, normalizes it, and routes it to <em>outputSender</em> via the NMR. This component combined with <em>outputSender</em> and supporting beans creates a JMS bridge between two topics.</td>
+ <td class="confluenceTd"> This component uses <em>jencks</em> , the JCA container, to listen on port 61616 for a JMS message on the topic called "demo.org.servicemix.source." <em>inputReceiver</em> subscribes to the demo.org.servicemix.source topic. It takes the message, normalizes it, and routes it to <em>outputSender</em> via the NMR. This component combined with <em>outputSender</em> and supporting beans creates a JMS bridge between two topics. </td>
</tr>
<tr>
<td class="confluenceTd"><em>outputSender</em></td>
- <td class="confluenceTd">This component receives a normalized message from the NMR, marshals it into a JMS message using <em>jmsTemplate</em>, then publishes it on the ActiveMQ (JMS) topic called "demo.org.servicemix.result."</td>
+ <td class="confluenceTd"> This component receives a normalized message from the NMR, marshals it into a JMS message using <em>jmsTemplate</em>, then publishes it on the ActiveMQ (JMS) topic called "demo.org.servicemix.result." </td>
</tr>
<tr>
<td class="confluenceTd"><em>jmsTrace</em></td>
- <td class="confluenceTd">This component uses <em>jencks</em> to subscribe to the "demo.org.servicemix.result" topic and get messages. It then marshals the message into a normalized message and routes it via the NMR to the <em>trace</em> component.</td>
+ <td class="confluenceTd"> This component uses <em>jencks</em> to subscribe to the "demo.org.servicemix.result" topic and get messages. It then marshals the message into a normalized message and routes it via the NMR to the <em>trace</em> component. </td>
</tr>
<tr>
<td class="confluenceTd"><em>trace</em></td>
- <td class="confluenceTd">Receives normalized messages from <em>jmsTrace</em> via the NMR. It transforms the normalized message into a string and logs it to the console.</td>
+ <td class="confluenceTd"> Receives normalized messages from <em>jmsTrace</em> via the NMR. It transforms the normalized message into a string and logs it to the console. </td>
</tr>
<tr>
<td class="confluenceTd"><em>jencks</em></td>
- <td class="confluenceTd"> The <em>jencks</em> bean defines a JCA container. The JCA container allows you to configure thread pool size, configure a transaction manager, and configure a resource adapter. In this example, the resource adapter is an ActiveMQ adapter, however, another JMS listener could be configured instead. This adapter listens on port 61616 for JMS messages.</td>
+ <td class="confluenceTd"> The <em>jencks</em> bean defines a JCA container. The JCA container allows you to configure thread pool size, configure a transaction manager, and configure a resource adapter. In this example, the resource adapter is an ActiveMQ adapter, however, another JMS listener could be configured instead. This adapter listens on port 61616 for JMS messages. </td>
</tr>
<tr>
<td class="confluenceTd"><em>broker</em></td>
- <td class="confluenceTd">The <em>broker</em> bean uses the <tt>activemq.xml</tt> file to configure the message broker, which handles the JMS messages for the components that require JMS messaging services.</td>
+ <td class="confluenceTd"> The <em>broker</em> bean uses the <tt>activemq.xml</tt> file to configure the message broker, which handles the JMS messages for the components that require JMS messaging services. </td>
</tr>
<tr>
<td class="confluenceTd"><em>transactionManager</em></td>
- <td class="confluenceTd">This bean is configured to be the default transaction manager for the <em>jbi</em> container. <em>jencks</em> is configured to use the default transaction manager. This transaction manager provides transactional services between the resource adapter (in this case the ActiveMQ resource adapter provided by the <em>jencks</em> JCA container) and components the <em>jbi</em> container. </td>
+ <td class="confluenceTd"> This bean is configured to be the default transaction manager for the <em>jbi</em> container. <em>jencks</em>is configured to use the default transaction manager. This transaction manager provides transactional services between the resource adapter (in this case the ActiveMQ resource adapter provided by the <em>jencks</em> JCA container) and components the <em>jbi</em> container. </td>
</tr>
<tr>
<td class="confluenceTd"><em>jmsFactory</em></td>
- <td class="confluenceTd">This bean listens on port 61616 and provides a pooled ActiveMQ connection.</td>
+ <td class="confluenceTd"> This bean listens on port 61616 and provides a pooled ActiveMQ connection. </td>
</tr>
</tbody>
</table>
@@ -376,7 +382,7 @@
<p>1. <em>jmsTemplate:</em> JmsTemplate is a Spring component which hides the low level details when sending JMS messages. For additional information see: <span class="nobr"><a href="http://activemq
.codehaus.org/Spring+Support" rel="nofollow" title="Visit page outside Confluence">JmsTemplate</a></span>. jmsTemplate is not a component in the <em>jbi</em> container. It is used by <em>inputSender</em> and <em>outputSender</em>.</p>
<h3><a name="Basic-Issues"></a>Issues</h3>
- <p>The ServiceMix 2.0.2 distribution has a known logging bug, so output is not logged to the console. This can be corrected in the <b>source</b> distribution of ServiceMix 2.0.2, by replacing the jencks-all-1.1.1.jar with the jencks-all-1.1.2.jar file. Upgrading to 2.0.3 will also resolve the problem. 2.0.3 release is a developer's release at this time. Please see <a href="Download" title="Download">Download</a> for the latest developer's release.</p>
+ <p>The ServiceMix 2.0.2 distribution has a known logging bug, so output is not logged to the console. This can be corrected in the <b>source</b>distribution of ServiceMix 2.0.2, by replacing the jencks-all-1.1.1.jar with the jencks-all-1.1.2.jar file. Upgrading to 2.0.3 will also resolve the problem. 2.0.3 release is a developer's release at this time. Please see <a href="Download" title="Download">Download</a> for the latest developer's release.</p>
<p>This procedure explains the work around for 2.0.2.</p>
<p class="paragraph">
<ol>
@@ -392,6 +398,7 @@
..\..\bin\servicemix servicemix.xml</pre></div>
</div>
</p>
+ <p> </p>
<p>Note: It is not necessary to build the source distribution if you have previously done so. If ServiceMix has not been built, execute the above steps before building. The procedure on how to build the source distribution can be found <span class="nobr"><a href="http://www.servicemix.org/Getting+Started#GettingStarted-WindowsSourceInstallation" rel="nofollow">here</a></span>.</p>
<h3><a name="Basic-RelatedDocumentation"></a>Related Documentation</h3>
<p>For more information on the following topics please see:</p>
Modified: incubator/servicemix/site/Client+API
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/Client%2BAPI?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/Client+API (original)
+++ incubator/servicemix/site/Client+API Mon Feb 27 22:52:24 2006
@@ -214,8 +214,8 @@
<div>
<div id="Content">
- <p>To make it simpler to use as an end user, we've created a JBI <span class="nobr"><a href="http://servicemix.codehaus.org/maven/apidocs/org/servicemix/client/ServiceMixClient.html" rel="nofollow">Client API</a></span> which makes it easy to work with any JBI container and other JBI components.</p>
- <p>The JavaDoc is probably self evident for many things, especially if you are aware of the JBI APIs. There is an <span class="nobr"><a href="http://servicemix.codehaus.org/maven/xref-test/org/servicemix/client/ServiceMixClientTest.html" rel="nofollow">example test case</a></span> which shows many of these APIs in action.</p>
+ <p>To make it simpler to use as an end user, we've created a JBI <span class="nobr"><a href="http://servicemix.org/maven/servicemix-core/apidocs/org/apache/servicemix/client/ServiceMixClient.html" rel="nofollow">Client API</a></span> which makes it easy to work with any JBI container and other JBI components.</p>
+ <p>The JavaDoc is probably self evident for many things, especially if you are aware of the JBI APIs. There is an <span class="nobr"><a href="http://servicemix.codehaus.org/maven/servicemix-core/xref-test/org/apache/servicemix/client/ServiceMixClientTest.html" rel="nofollow">example test case</a></span> which shows many of these APIs in action.</p>
<h2><a name="ClientAPI-UsingtheJBIinterfaces"></a>Using the JBI interfaces</h2>
<p>The following helper methods just provide some helper methods for easier use of the JBI APIs</p>
<h3><a name="ClientAPI-Sendingmessages"></a>Sending messages</h3>
@@ -289,7 +289,7 @@
<h3><a name="ClientAPI-Invokingservices"></a>Invoking services</h3>
<p class="paragraph">
<div class="code">
- <div class="codeContent"><pre class="code-java"><span class="code-comment">// optional endpoint resolution
+ <div class="codeContent"><pre class="code-java"><span class="code-comment">// optional endpoint resolution
</span>EndpointResolver resolver = client.createResolverForService(service);
Map properties = <span class="code-keyword">new</span> HashMap();
@@ -301,10 +301,25 @@
<h2><a name="ClientAPI-ConfiguringtheServiceMixClient"></a>Configuring the ServiceMixClient</h2>
<p>We use the Spring XML configuration files to configure the client. You can then use dependency injection to inject the client into your POJOs.</p>
<p>Here's an example of using a basic client...</p>
- <p class="paragraph"> [Unable to download http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-core/src/test/resources/org/servicemix/client/example.xml : http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-core/src/test/resources/org/servicemix/client/example.xml] </p>
+ <p class="paragraph">
+ <div class="code">
+ <div class="codeContent"><pre class="code-xml"><span class="code-tag"><bean id=<span class="code-quote">"client"</span> class=<span class="code-quote">"org.apache.servicemix.client.DefaultServiceMixClient"</span>></span>
+ <span class="code-tag"><constructor-arg ref=<span class="code-quote">"jbi"</span> /></span>
+<span class="code-tag"></bean></span></pre></div>
+ </div>
+ </p>
<p>Note that the jbi bean reference is the ServiceMix JBI container.</p>
<p>This example creates a client which is hard-wired to default to a specific service when an invocation is performed.</p>
- <p class="paragraph"> [Unable to download http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-core/src/test/resources/org/servicemix/client/example.xml : http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-core/src/test/resources/org/servicemix/client/example.xml] </p>
+ <p class="paragraph">
+ <div class="code">
+ <div class="codeContent"><pre class="code-xml"><span class="code-tag"><bean id=<span class="code-quote">"clientWithRouting"</span> class=<span class="code-quote">"org.apache.servicemix.client.DefaultServiceMixClient"</span>></span>
+ <span class="code-tag"><constructor-arg ref=<span class="code-quote">"jbi"</span> /></span>
+ <span class="code-tag"><constructor-arg></span>
+ <span class="code-tag"><sm:activationSpec destinationService=<span class="code-quote">"foo:receiver"</span>/></span>
+ <span class="code-tag"></constructor-arg></span>
+<span class="code-tag"></bean></span></pre></div>
+ </div>
+ </p>
</div>
</div>
Modified: incubator/servicemix/site/Container+MBean
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/Container%2BMBean?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/Container+MBean (original)
+++ incubator/servicemix/site/Container+MBean Mon Feb 27 22:52:24 2006
@@ -214,8 +214,88 @@
<div>
<div id="Content">
+ <p>The JBIContainer MBean is uses the <a href="Life+Cycle+MBean" title="Life Cycle MBean">Life Cycle MBean</a>for life cycle management. All life cycle operations (start,stop,shutdown) are recursively applied to all the contained Components and internal services of the Container.</p>
<p>
- <br> The JBIContainer MBean is uses the <a href="Life+Cycle+MBean" title="Life Cycle MBean">Life Cycle MBean</a> for life cycle management. All life cycle operations (start,stop,shutdown) are recursively applied to all the contained Components and internal services of the Container.</p>
+ <br clear="all">
+ </p>
+ <p class="paragraph">
+ <table align="center" border=0 cellpadding=5 cellspacing="8px" class="infoMacro" width="85%">
+ <colgroup>
+ <col width=24>
+ <col>
+ </colgroup>
+ <tr>
+ <td valign="top"><img align="absmiddle" alt="" border=0 height=16 src="http://www.servicemix.org/images/icons/emoticons/information.gif" width=16></td>
+ <td><b class="strong">Operations</b><br>
+ <table class="confluenceTable">
+ <tbody>
+ <tr>
+ <th class="confluenceTh"> Name </th>
+ <th class="confluenceTh"> Parameters </th>
+ <th class="confluenceTh"> Signature </th>
+ <th class="confluenceTh"> Description </th>
+ </tr>
+ <tr>
+ <td class="confluenceTd"> start </td>
+ <td class="confluenceTd"> void </td>
+ <td class="confluenceTd"> void </td>
+ <td class="confluenceTd"> starts processing </td>
+ </tr>
+ <tr>
+ <td class="confluenceTd"> stop </td>
+ <td class="confluenceTd"> void </td>
+ <td class="confluenceTd"> void </td>
+ <td class="confluenceTd"> stop the container from processing </td>
+ </tr>
+ <tr>
+ <td class="confluenceTd"> shutDown </td>
+ <td class="confluenceTd"> void </td>
+ <td class="confluenceTd"> void </td>
+ <td class="confluenceTd"> shutdowns the container from processing </td>
+ </tr>
+ </tbody>
+ </table>
+ </td>
+ </tr>
+ </table>
+ </p>
+ <br clear="all">
+ <p class="paragraph">
+ <table align="center" border=0 cellpadding=5 cellspacing="8px" class="infoMacro" width="85%">
+ <colgroup>
+ <col width=24>
+ <col>
+ </colgroup>
+ <tr>
+ <td valign="top"><img align="absmiddle" alt="" border=0 height=16 src="http://www.servicemix.org/images/icons/emoticons/information.gif" width=16></td>
+ <td><b class="strong">Attributes</b><br>
+ <table class="confluenceTable">
+ <tbody>
+ <tr>
+ <th class="confluenceTh"> Name </th>
+ <th class="confluenceTh"> type </th>
+ <th class="confluenceTh"> read/write </th>
+ <th class="confluenceTh"> Description </th>
+ </tr>
+ <tr>
+ <td class="confluenceTd"> capacity </td>
+ <td class="confluenceTd"> int </td>
+ <td class="confluenceTd"> read/write </td>
+ <td class="confluenceTd"> the default Capacity for MessageExchanges for all SedaQueues </td>
+ </tr>
+ <tr>
+ <td class="confluenceTd"> queueNumber </td>
+ <td class="confluenceTd"> int </td>
+ <td class="confluenceTd"> read-only </td>
+ <td class="confluenceTd"> the number of SedaQueues running </td>
+ </tr>
+ </tbody>
+ </table>
+ </td>
+ </tr>
+ </table>
+ </p>
+ <br clear="all">
</div>
</div>
Modified: incubator/servicemix/site/Glossary
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/Glossary?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/Glossary (original)
+++ incubator/servicemix/site/Glossary Mon Feb 27 22:52:24 2006
@@ -242,6 +242,10 @@
<td class="confluenceTd"> Contributor License Agreement see: <span class="nobr"><a href="http://www.apache.org/licenses/" rel="nofollow">http://www.apache.org/licenses/</a></span></td>
</tr>
<tr>
+ <td class="confluenceTd">Drools <a name="Glossary-Drools"></a></td>
+ <td class="confluenceTd">A rules engine implementation. The idea is to expose a DroolsComponent at some service/interface/operation endpoint in ServiceMix then let it perform rules based routing, or other actions as required.</td>
+ </tr>
+ <tr>
<td class="confluenceTd">EDA <a name="Glossary-EDA"></a></td>
<td class="confluenceTd">An Event Driven Architecture is an approach for designing and building applications in which events trigger messages to be sent between decoupled applications. Event messages are typically sent using a publish-and-subscribe method such as JMS topics. EDA interactions are asynchronous in nature, whereas the loosely-coupled SOA interactions are usually synchronous (request/response). In EDA transactions, messages can be queued and delivered later.</td>
</tr>
@@ -262,10 +266,18 @@
<td class="confluenceTd"> The Apache Geronimo application server. See <span class="nobr"><a href="http://geronimo.apache.org/" rel="nofollow">http://geronimo.apache.org/</a></span></td>
</tr>
<tr>
+ <td class="confluenceTd">Groovy <a name="Glossary-Groovy"></a></td>
+ <td class="confluenceTd">A scripting language for Java2 platform. Making features similar to Python, Ruby and Smalltalk languages available to developers in a Java-like syntax.</td>
+ </tr>
+ <tr>
<td class="confluenceTd">J2EE <a name="Glossary-J2EE"></a></td>
<td class="confluenceTd">Java 2 Enterprise Edition, old name for Java EE</td>
</tr>
<tr>
+ <td class="confluenceTd">Jabber <a name="Glossary-Jabber"></a></td>
+ <td class="confluenceTd">Open Source instant messaging component</td>
+ </tr>
+ <tr>
<td class="confluenceTd">JAX-WS</td>
<td class="confluenceTd"><span class="nobr"><a href="http://jcp.org/aboutJava/communityprocess/pfd/jsr224/index.html" rel="nofollow">JSR 224</a></span>: Java API for XML-based Web Services</td>
</tr>
@@ -282,10 +294,18 @@
<td class="confluenceTd">Java Business Integration (described in JSR 208)</td>
</tr>
<tr>
+ <td class="confluenceTd">JCA <a name="Glossary-JCA"></a></td>
+ <td class="confluenceTd">The JCA Java Connector Architecture provides the most efficient way of thread pooling, resource pooling, transaction handling and consumption on JMS and other Resource Adapters.</td>
+ </tr>
+ <tr>
<td class="confluenceTd">JMS <a name="Glossary-JMS"></a></td>
<td class="confluenceTd">Java Messaging Service API</td>
</tr>
<tr>
+ <td class="confluenceTd">JMX <a name="Glossary-JMX"></a></td>
+ <td class="confluenceTd">Java Management Extensions provides tools for building distributed, Web-based, modular and dynamic solutions for managing and monitoring devices, applications, and service-driven networks.</td>
+ </tr>
+ <tr>
<td class="confluenceTd">JSR 208 <a name="Glossary-JSR208"></a></td>
<td class="confluenceTd"><span class="nobr"><a href="http://www.jcp.org/en/jsr/detail?id=208" rel="nofollow">Java Specification Request #208</a></span>, "defines a standard meta container for SOA-based applications through the Service Assembly, also known as a composite service description. JBI enables collaboration between different integration technologies through standard Message Exchange Patterns (MEP) and Service Provider Interfaces (SPI)s for Service Engines and Binding Components." (<span class="nobr"><a href="http://java.sun.com/integration/download/index.html" rel="nofollow">http://java.sun.com/integration/download/index.html</a></span>)</td>
</tr>
@@ -324,12 +344,20 @@
<td class="confluenceTd">Plain Old Java Objects</td>
</tr>
<tr>
+ <td class="confluenceTd">Quartz <a name="Glossary-Quartz"></a></td>
+ <td class="confluenceTd">Open source job scheduling system that can be integrated with, or used along side virtually any J2EE or J2SE application.</td>
+ </tr>
+ <tr>
+ <td class="confluenceTd">Reflection <a name="Glossary-Reflection"></a></td>
+ <td class="confluenceTd">The reflection API represents, or reflects, the classes, interfaces, and objects in the current Java Virtual Machine. This API is handy if you are writing development tools such as debuggers, class browsers, and GUI builders</td>
+ </tr>
+ <tr>
<td class="confluenceTd">Routing <a name="Glossary-routing"></a></td>
<td class="confluenceTd">Intelligent or content-based routing is the process of making appropriate path and/or destination decisions based on the content of the message being transported. The path/route taken will is decided by the ESB after analyzing the message content and metadata.</td>
</tr>
<tr>
<td class="confluenceTd">RSS <a name="Glossary-RSS"></a></td>
- <td class="confluenceTd">RDF Site Summary, or Rich Site Summary, or Really Simple Syndication – A lightweight XML format for distributing news headlines and other content on the Web.</td>
+ <td class="confluenceTd">RDF Site Summary, or Rich Site Summary, or Really Simple Syndication - A lightweight XML format for distributing news headlines and other content on the Web.</td>
</tr>
<tr>
<td class="confluenceTd">SAAJ <a name="Glossary-SAAJ"></a></td>
@@ -340,6 +368,10 @@
<td class="confluenceTd"> A service-oriented architecture is a software architectural concept where composite web applications are developed as a collection of services that can be independently developed, deployed, discovered and even replaced. The services typically support one aspect of a business requirement or process and while the internals of the service can be implemented in any number of ways, the interface to other components that use the service generally conforms to a standard such as Web Services.</td>
</tr>
<tr>
+ <td class="confluenceTd">SOAP <a name="Glossary-SOAP"></a></td>
+ <td class="confluenceTd">Protocol for exchanging XML-based messages over a computer network, normally using HTTP.</td>
+ </tr>
+ <tr>
<td class="confluenceTd">Spring <a name="Glossary-Spring"></a></td>
<td class="confluenceTd"> An Open Source framework for developing Java applications, especially favorable to POJOs. See <span class="nobr"><a href="http://www.springframework.org/about" rel="nofollow">http://www.springframework.org/about</a></span></td>
</tr>
@@ -356,12 +388,32 @@
<td class="confluenceTd"> Data Transformation is the process of taking data from one representation and translating it into another, while retaining the integrity of the information. This is most often required when applications use semantically similar data in different formats, e.g. application A identifies an "Employee" by driver's license number while application B identifies an employee by social security number. The transformation component offers the flexibility and opportunity to change data to any desired format for any desired reason.</td>
</tr>
<tr>
+ <td class="confluenceTd">UDDI <a name="Glossary-UDDI"></a></td>
+ <td class="confluenceTd">Universal Description, Discovery and Integration Is A Web-based distributed directory that enables businesses to list themselves on the Internet. Similar to the yellow pages.</td>
+ </tr>
+ <tr>
<td class="confluenceTd">Web Services <a name="Glossary-webservices"></a></td>
<td class="confluenceTd"> Web Services refers to a suite of XML-based standards that allow applications to exchange information in a platform independent way. Early work in Web Services focused on standards for service description (WSDL), deployment and discovery (UDDI). The effort has expanded to include standards for security, reliability and management among others. Web services are typically invoked over the Internet using standard protocols, most often SOAP (Simple Object Access Protocol). </td>
</tr>
<tr>
+ <td class="confluenceTd">WSDL <a name="Glossary-WSDL"></a></td>
+ <td class="confluenceTd">Web Services Description language.</td>
+ </tr>
+ <tr>
<td class="confluenceTd">WSIF <a name="Glossary-WSIF"></a></td>
<td class="confluenceTd">Web Services Invocation Framework: a Java API that enables dynamic invocation or updating of a Web Service at runtime. It follows the semantics of WSDL as much as possible. It is meant to be used when the semantics of WSDL do not suffice and need to be extended.</td>
+ </tr>
+ <tr>
+ <td class="confluenceTd">XFire <a name="Glossary-XFire"></a></td>
+ <td class="confluenceTd">XFire is an easy-to-use SOAP framework that offers high performance.</td>
+ </tr>
+ <tr>
+ <td class="confluenceTd">XSLT <a name="Glossary-XSLT"></a></td>
+ <td class="confluenceTd">XML based language used for transforming XML documents. The original document is not modified in the process of building a new document based on the information in the original.</td>
+ </tr>
+ <tr>
+ <td class="confluenceTd">XSQL <a name="Glossary-XSQL"></a></td>
+ <td class="confluenceTd">Tool for turning SQL queries into XML or for inserting/updating XML into a database.</td>
</tr>
</tbody>
</table>
Modified: incubator/servicemix/site/Home
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/Home?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/Home (original)
+++ incubator/servicemix/site/Home Mon Feb 27 22:52:24 2006
@@ -267,6 +267,15 @@
</ul>
<h2><a name="Home-News"></a>News</h2>
<p class="paragraph">
+ <div class="greybox"> <span>Wednesday, February 15, 2006</span></div>
+ <div class="blogpost" style="margin-bottom: 30px">
+ <div class="blogHeading" style="margin-top: 0px; padding-top: 0px"><a href="http://docs.codehaus.org/display/SM/2006/02/15/Creating+graphical+JBI+deployments+with+ServiceMix+in+Eclipse" style="text-decoration: none; color: black">Creating graphical JBI deployments with ServiceMix in Eclipse</a></div>
+ <div class="pagesubheading">
+ </div>
+ <div class="wiki-content">
+ <p>Philip Dodds has a <span class="nobr"><a href="http://www.fiveclouds.com/articles/2006/02/11/servicemix-deployments-in-eclipse" rel="nofollow">great article</a></span> showing ServiceMix deployments being created in <span class="nobr"><a href="http://www.eclipse.org/" rel="nofollow">Eclipse</a></span>. Go Philip!</p>
+ </div>
+ </div>
<div class="greybox"> <span>Wednesday, January 25, 2006</span></div>
<div class="blogpost" style="margin-bottom: 30px">
<div class="blogHeading" style="margin-top: 0px; padding-top: 0px"><a href="http://docs.codehaus.org/display/SM/2006/01/25/ServiceMix+at+JavaWorld" style="text-decoration: none; color: black">ServiceMix at JavaWorld</a></div>
@@ -302,15 +311,6 @@
<p>We have now moved the <a href="Source" title="Source">Source</a> of ServiceMix to Apache. You can surf and checkout the latest code from here</p>
<p><span class="nobr"><a href="https://svn.apache.org/repos/asf/incubator/servicemix/" rel="nofollow">https://svn.apache.org/repos/asf/incubator/servicemix/</a></span></p>
<p>Also we now have a set of Apache based <a href="Mailing+Lists" title="Mailing Lists">Mailing Lists</a></p>
- </div>
- </div>
- <div class="greybox"> <span>Wednesday, November 23, 2005</span></div>
- <div class="blogpost" style="margin-bottom: 30px">
- <div class="blogHeading" style="margin-top: 0px; padding-top: 0px"><a href="http://docs.codehaus.org/display/SM/2005/11/23/ServiceMix+discussion+forum+open" style="text-decoration: none; color: black">ServiceMix discussion forum open</a></div>
- <div class="pagesubheading">
- </div>
- <div class="wiki-content">
- <p>There is a new <span class="nobr"><a href="http://forums.logicblaze.com/forums/show/3.page" rel="nofollow">discussion forum</a></span> now open to dicusss all things ServiceMix, ESB or JBI. </p>
</div>
</div>
<hr>
Modified: incubator/servicemix/site/How+does+ServiceMix+compare+to+Celtix
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/How%2Bdoes%2BServiceMix%2Bcompare%2Bto%2BCeltix?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/How+does+ServiceMix+compare+to+Celtix (original)
+++ incubator/servicemix/site/How+does+ServiceMix+compare+to+Celtix Mon Feb 27 22:52:24 2006
@@ -215,10 +215,10 @@
<div>
<div id="Content">
<p><span class="nobr"><a href="http://celtix/objectweb.org/" rel="nofollow">Celtix</a></span> is an open source ESB project founded by <span class="nobr"><a href="http://www.iona.com" rel="nofollow">Iona</a></span>, and hosted at <span class="nobr"><a href="http://www.objectweb.org/" rel="nofollow">ObjectWeb</a></span>. Like ServiceMix, Celtix is designed to serve as the foundation for a Service Oriented Architecture. Although the two project teams are both developing ESB solutions, there is a close level of collaboration between the two efforts, due to the complementary nature of the projects.</p>
- <p>The ServiceMix development effort has focused on providing an ESB based on a JBI container and component suite. Celtix is focused on integration components and SOAP stacks. This means that there is actually not as much overlap between the two projects as one might expect. On the contrary, the two project teams are collaborating closely to avoid duplicating efforts and to enable reuse of each project’s unique capabilities. For example, ServiceMix will reuse the SOAP stacks and integration components from Celtix, and Celtix will reuse the ServiceMix JBI container.</p>
+ <p>The ServiceMix development effort has focused on providing an ESB based on a JBI container and component suite. Celtix is focused on integration components and SOAP stacks. This means that there is actually not as much overlap between the two projects as one might expect. On the contrary, the two project teams are collaborating closely to avoid duplicating efforts and to enable reuse of each project's unique capabilities. For example, ServiceMix will reuse the SOAP stacks and integration components from Celtix, and Celtix will reuse the ServiceMix JBI container.</p>
<p>Why is ServiceMix focused on JBI? The ServiceMix team began work on its ESB solution at the time that the JBI specification was in discussion, so the team was able to plan on using JBI not only for integration capabilities at the endpoints, but also for internal APIs, to enable JBI-compliant solutions to deliver core functionality to the integration environment.</p>
<p>For example, because JBI supports a standard deployment unit format, ServiceMix supports hot deployment of any JBI-compliant BPEL engine (or set of BPEL files into a BPEL engine), rule engine, transformation engine, scripting engine or other integration component (such as specific JBI binding components) directly into ServiceMix. Also, ServiceMix contains a number of WS-* implementations built on JBI, such as WS Notification.</p>
- <p>Today’s Open Source ESB solutions are increasingly focused on interoperability. Despite the different approaches to integration that the ServiceMix and Celtix teams have taken, the advantage they enjoy as open source projects through close collaboration is the ability to leverage each other’s strengths.</p>
+ <p>Today's Open Source ESB solutions are increasingly focused on interoperability. Despite the different approaches to integration that the ServiceMix and Celtix teams have taken, the advantage they enjoy as open source projects through close collaboration is the ability to leverage each other's strengths.</p>
</div>
</div>
Modified: incubator/servicemix/site/How+does+ServiceMix+compare+to+Mule
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/How%2Bdoes%2BServiceMix%2Bcompare%2Bto%2BMule?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/How+does+ServiceMix+compare+to+Mule (original)
+++ incubator/servicemix/site/How+does+ServiceMix+compare+to+Mule Mon Feb 27 22:52:24 2006
@@ -221,7 +221,7 @@
<p>For example, because JBI supports a standard deployment unit format, you can hot deploy any JBI-compliant BPEL engine (or set of BPEL files into a BPEL engine), rule engine, transformation engine, scripting engine or other integration component (such as specific JBI binding components) directly into ServiceMix. Also ServiceMix contains a number of WS-* implementations built on JBI, such as WS Notification.</p>
<p>Even though the JBI standard and the Mule messaging platform look very different at the API level, conceptually they are trying to do similar things. Like Mule, JBI is based on the idea of both component and container based routing. However, JBI provides a standard for the integration of any commercial or open source component. Equally important, the JBI standard supports a very high level of integration functionality. A JBI component can perform smart routing to endpoints. A JBI component can just communicate with its default service, letting the container do the routing for it. Or a JBI component can give the JBI container a hint of which endpoint to use (such as providing a service QName to use or specifying an operation QName) and then the JBI container can, if there are many available services to choose from, use some kind of policy negotiation or load balancing algorithm to choose which physical endpoint to choose. Lastly, JBI is a cleaner abstraction for workin
g with both logical and physical web service endpoints, WSDL and the standard WSDL defined message exchange patterns (MEPs).</p>
<p>While ServiceMix supports a lightweight deployment model similar to that of Mule, ServiceMix is also fully integrated into Apache Geronimo, bringing JBI functionality into Apache's J2EE container. This allows Apache Geronimo to hot-deploy any JBI component or service using its standard deployment tooling (JSR 77/88 compliant). This difference between the two products also originates in our focus on agility. Some ServiceMix implementations will be endpoint-centric, like Mule. Others may leverage the capabilities of an application server. ServiceMix is designed for either integration scenario, or some combination of the two.</p>
- <p>Today’s Open Source ESB solutions are increasingly focused on interoperability, and despite their differences in architecture and design philosophy, this principle of interoperability applies to ServiceMix and Mule. The Mule JBI binding enables Mule components to interact with the ServiceMix JBI container. Also, Mule transports, components and transformers can be used inside the ServiceMix JBI container. Likewise, ServiceMix has full support for Mule; so if you already have an investment in some Mule configuration or code, you can reuse it inside ServiceMix along with any other JBI components.</p>
+ <p>Today's Open Source ESB solutions are increasingly focused on interoperability, and despite their differences in architecture and design philosophy, this principle of interoperability applies to ServiceMix and Mule. The Mule JBI binding enables Mule components to interact with the ServiceMix JBI container. Also, Mule transports, components and transformers can be used inside the ServiceMix JBI container. Likewise, ServiceMix has full support for Mule; so if you already have an investment in some Mule configuration or code, you can reuse it inside ServiceMix along with any other JBI components.</p>
</div>
</div>
Modified: incubator/servicemix/site/How+does+ServiceMix+compare+to+Synapse
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/How%2Bdoes%2BServiceMix%2Bcompare%2Bto%2BSynapse?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/How+does+ServiceMix+compare+to+Synapse (original)
+++ incubator/servicemix/site/How+does+ServiceMix+compare+to+Synapse Mon Feb 27 22:52:24 2006
@@ -228,6 +228,7 @@
</p>
<p> </p>
<p> </p>
+ <p> </p>
<p>The distinction David makes goes to the heart of both questions. First, Synapse is not a full ESB in the most common sense of the term. Secondly, because the design of Apache Synapse is different from that of Apache ServiceMix, the two solutions have different capabilities and limitations.</p>
<p>A number of solutions that broker or mediate Web services exchanges are described as ESBs, and Synapse can reasonably be included in that category. However, what most defines an ESB is not its architecture, but its function, which in general terms is to provide</p>
<ul class="alternate" type="square">
@@ -235,9 +236,7 @@
<li>with a high degree of performance, scalability and reliability</li>
<li>spanning multiple transports and heterogeneous endpoints.</li>
</ul>
- <p>In providing management through WS-* to Apache Axis, Apache Synapse provides a very important and useful capability to that specific Web service broker. However, in its current implementation Apache Synapse would be overextended as an "architectural" solution. Building an SOA on Apache Synapse would presume that all exchanges in the SOA would be Web Service exchanges based on SOAP, that the management of the exchanges would be invoked exclusively by means of WS-*, </p>
- <p class="paragraph">
- <del>and that the underlying SOAP technology at each brokered endpoint would be Apache Axis2</del> *ANY* SOAP stack which implements the relevant protocols. </p>
+ <p>In providing management through WS-* to Apache Axis, the Apache Synapse project provides a very important and useful capability to Web services. However, in its current implementation Apache Synapse would be overextended as an "architectural" solution. Building an SOA on Apache Synapse would presume that all exchanges in the SOA would be made through SOAP-based Web Services, that the management of the exchanges would be invoked exclusively by means of WS-*, and that the underlying SOAP stack(s) implement the relevant protocols.</p>
<p>ServiceMix is a full ESB that can work with many different <a href="Components" title="Components">SOAP Stacks</a> such as Axis, WSIF, XFire, ActiveSOAP and JAX-WS. ServiceMix also has full support for <a href="Routing" title="Routing">Routing</a>, <a href="Transformation" title="Transformation">Transformation</a> and <a href="BPEL" title="BPEL">Orchestration</a>. Like Apache Synapse, Apache ServiceMix provides mediation for web services exchanges and is designed to support transformation, management and routing through WS-* standards. However, this capability is provided without dependency on the SOAP stack, and most importantly, is provided through the same services architecture used for all message formats and transports, including, but certainly not limited to, Web services.</p>
<p>Lastly, it is also worth noting that the ServiceMix <a href="Team" title="Team">Team</a> are working with the Synapse community to add JBI support to Synapse, so ServiceMix and Synapse could work together and integrate nicely with each other using JBI; deploying Synase as a JBI component within ServiceMix's JBI container allowing it to integrate with other JBI components such as smart routers or BPEL engines etc.</p>
</div>
Modified: incubator/servicemix/site/I+can+not+create+a+JIRA+issue
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/I%2Bcan%2Bnot%2Bcreate%2Ba%2BJIRA%2Bissue?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/I+can+not+create+a+JIRA+issue (original)
+++ incubator/servicemix/site/I+can+not+create+a+JIRA+issue Mon Feb 27 22:52:24 2006
@@ -244,3 +244,4 @@
</html>
+
Modified: incubator/servicemix/site/InstallComponentTask
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/InstallComponentTask?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/InstallComponentTask (original)
+++ incubator/servicemix/site/InstallComponentTask Mon Feb 27 22:52:24 2006
@@ -233,7 +233,8 @@
<th class="confluenceTh"> Description </th>
</tr>
<tr>
- <td class="confluenceTd"> archivePath </td>
+ <td class="confluenceTd"> file <br clear="all">
+ </td>
<td class="confluenceTd"> String </td>
<td class="confluenceTd"> the archive path for the Component archive </td>
</tr>
@@ -243,6 +244,8 @@
</tr>
</table>
</p>
+ <br>
+ <p class="paragraph"> </p>
</div>
</div>
Modified: incubator/servicemix/site/InstallSharedLibraryTask
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/InstallSharedLibraryTask?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/InstallSharedLibraryTask (original)
+++ incubator/servicemix/site/InstallSharedLibraryTask Mon Feb 27 22:52:24 2006
@@ -233,7 +233,8 @@
<th class="confluenceTh"> Description </th>
</tr>
<tr>
- <td class="confluenceTd"> sharedLibURI </td>
+ <td class="confluenceTd"> file <br clear="all">
+ </td>
<td class="confluenceTd"> String </td>
<td class="confluenceTd"> theURI of the shared library to install </td>
</tr>
@@ -243,6 +244,8 @@
</tr>
</table>
</p>
+ <br>
+ <p class="paragraph"> </p>
</div>
</div>
Modified: incubator/servicemix/site/Management
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/Management?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/Management (original)
+++ incubator/servicemix/site/Management Mon Feb 27 22:52:24 2006
@@ -218,7 +218,7 @@
<h3><a name="Management-JMXConsole"></a>JMXConsole</h3>
<p><a href="JMX+Console" title="JMX Console">JMX Console</a> - infomation about connecting to JMX from an application of management console</p>
<h3><a name="Management-MBeans"></a>MBeans</h3>
- <p>The following provides infomation on the MBean operation and attributes exposed via JMX within servicemix. <br clear="all"><a href="Life+Cycle+MBean" title="Life Cycle MBean">Life Cycle MBean</a><br><a href="Component+MBean" title="Component MBean">Component MBean</a><br><a href="Container+MBean" title="Container MBean">Container MBean</a><br><a href="Environment+MBean" title="Environment MBean">Environment MBean</a><br><a href="NMR+Broker+MBean" title="NMR Broker MBean">NMR Broker MBean</a><br><a href="Message+Flow+MBean" title="Message Flow MBean">Message Flow MBean</a></p>
+ <p>The following provides infomation on the MBean operation and attributes exposed via JMX within servicemix. <br clear="all"><a href="Life+Cycle+MBean" title="Life Cycle MBean">Life Cycle MBean</a><br><a href="Component+MBean" title="Component MBean">Component MBean</a><br><a href="Container+MBean" title="Container MBean">Container MBean</a><br><a href="Environment+Context+MBean" title="Environment Context MBean">Environment Context MBean</a><br><a href="NMR+Broker+MBean" title="NMR Broker MBean">NMR Broker MBean</a><br><a href="Message+Flow+MBean" title="Message Flow MBean">Message Flow MBean</a></p>
<h3><a name="Management-Statistics"></a>Statistics</h3>
<p>If ServiceMix is configured (see <a href="Configuration" title="Configuration">Configuration</a>) to dump statistics, it will for individual component's in their running directory into the file Stats.csv. Statistics measure inbound/outbound exchange rates for a component's DeliveryChannel. The format of the statistics dumped is:</p>
<p class="paragraph">
Modified: incubator/servicemix/site/News
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/News?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/News (original)
+++ incubator/servicemix/site/News Mon Feb 27 22:52:24 2006
@@ -215,6 +215,15 @@
<div>
<div id="Content">
<p class="paragraph">
+ <div class="greybox"> <span>Wednesday, February 15, 2006</span></div>
+ <div class="blogpost" style="margin-bottom: 30px">
+ <div class="blogHeading" style="margin-top: 0px; padding-top: 0px"><a href="http://docs.codehaus.org/display/SM/2006/02/15/Creating+graphical+JBI+deployments+with+ServiceMix+in+Eclipse" style="text-decoration: none; color: black">Creating graphical JBI deployments with ServiceMix in Eclipse</a></div>
+ <div class="pagesubheading">
+ </div>
+ <div class="wiki-content">
+ <p>Philip Dodds has a <span class="nobr"><a href="http://www.fiveclouds.com/articles/2006/02/11/servicemix-deployments-in-eclipse" rel="nofollow">great article</a></span> showing ServiceMix deployments being created in <span class="nobr"><a href="http://www.eclipse.org/" rel="nofollow">Eclipse</a></span>. Go Philip!</p>
+ </div>
+ </div>
<div class="greybox"> <span>Wednesday, January 25, 2006</span></div>
<div class="blogpost" style="margin-bottom: 30px">
<div class="blogHeading" style="margin-top: 0px; padding-top: 0px"><a href="http://docs.codehaus.org/display/SM/2006/01/25/ServiceMix+at+JavaWorld" style="text-decoration: none; color: black">ServiceMix at JavaWorld</a></div>
@@ -320,16 +329,6 @@
<li><a href="Use+Cases" title="Use Cases">Use Cases</a></li>
<li><a href="Tomcat+Integration" title="Tomcat Integration">Tomcat Integration</a></li>
</ul>
- </div>
- </div>
- <div class="greybox"> <span>Tuesday, September 13, 2005</span></div>
- <div class="blogpost" style="margin-bottom: 30px">
- <div class="blogHeading" style="margin-top: 0px; padding-top: 0px"><a href="http://docs.codehaus.org/display/SM/2005/09/13/The+ServiceMix+team+is+proud+to+support+the+SOA+Tooling+Project" style="text-decoration: none; color: black">The ServiceMix team is proud to support the SOA Tooling Project</a></div>
- <div class="pagesubheading">
- </div>
- <div class="wiki-content">
- <p>As well as our <span class="nobr"><a href="http://mail-archives.apache.org/mod_mbox/incubator-general/200508.mbox/%3c245FBCC4-1C5B-4085-8F4D-C46EA22EFF1D@mac.com%3e" rel="nofollow">support</a></span> and contributions to both <span class="nobr"><a href="http://celtix.objectweb.org" rel="nofollow">Celtix</a></span> and Apache Synapse, we're happy to announce our support for the Eclipse <span class="nobr"><a href="http://www.eclipse.org/proposals/stp/" rel="nofollow">SOA Tooling Project</a></span> to provide tooling for ESB and JBI. Our <a href="Team" title="Team">Team</a> is looking forward to working with the other <span class="nobr"><a href="http://www.eclipse.org/proposals/stp/" rel="nofollow">supporters</a></span> to make some great Eclipse tooling. </p>
- <p>BTW if you've not seen it yet the current <span class="nobr"><a href="http://www.eclipse.org/webtools/index.html" rel="nofollow">WebTools project</a></span> provides good JSP, web, XML, XSD, WSDL support and <span class="nobr"><a href="http://www.eclipse.org/birt/" rel="nofollow">BIRT</a></span> provides good reporting.</p>
</div>
</div>
</p>
Modified: incubator/servicemix/site/POJO+support
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/POJO%2Bsupport?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/POJO+support (original)
+++ incubator/servicemix/site/POJO+support Mon Feb 27 22:52:24 2006
@@ -361,7 +361,7 @@
<p> </p>
<h2><a name="POJOsupport-BeingevenmorePOJO"></a>Being even more POJO</h2>
<p>The code above may seem a bit too verbose for you. Firstly you can reduce much code by reusing the <a href="Component+helper+classes" title="Component helper classes">Component helper classes</a>.</p>
- <p>Another option is to be even more POJO-like. If you just want to invoke operations on the JBI bus then there's no need for you to implement the JBI component or lifecyclce contract - you can just reuse the <a href="Client+API" title="Client API">Client API</a>.</p>
+ <p>Another option is to be even more POJO-like. If you just want to invoke operations on the JBI bus then there's no need for you to implement the JBI component or lifecycle contract - you can just reuse the <a href="Client+API" title="Client API">Client API</a>.</p>
<p>For example this POJO sends messages into the JBI bus.</p>
<p class="paragraph">
<div class="code">
Modified: incubator/servicemix/site/Publish+Subscribe+Routing
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/Publish%2BSubscribe%2BRouting?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/Publish+Subscribe+Routing (original)
+++ incubator/servicemix/site/Publish+Subscribe+Routing Mon Feb 27 22:52:24 2006
@@ -216,26 +216,28 @@
<div id="Content">
<p>The normal routing mechanism in JBI uses <em>Queue Semantics</em>, that is each request is routed to one and only one endpoint.</p>
<p>ServiceMix supports an additional routing mechanism which uses <em>Topic Semantics</em>. That is every subscriber who is interested in the message receives a copy of the message.</p>
- <p>You can subscribe to the output of an endpoint as follows, using the <b><subscription service="<em>serviceQName</em>"/></b> tag. (You can include as many as you like inside a <b><component/></b> tag</p>
+ <p>You can subscribe to the output of an endpoint as follows, using the <b><subscriptionSpec service="</b><b><em>serviceQName</em></b><b>"/></b> tag. (You can include as many as you like inside a <b><subscriptions/></b> tag</p>
<p class="paragraph">
<div class="code">
- <div class="codeContent"><pre class="code-xml"><component id=<span class="code-quote">"receiver"</span> service=<span class="code-quote">"foo:receiver"</span>
- class=<span class="code-quote">"org.servicemix.examples.ReceiverComponent"</span>>
+ <div class="codeContent"><pre class="code-xml"><span class="code-tag"><sm:activationSpec componentName=<span class="code-quote">"receiver"</span> service=<span class="code-quote">"foo:receiver"</span>></span>
+ <span class="code-tag"><sm:component></span><span class="code-tag"><bean class=<span class="code-quote">"org.apache.servicemix.tck.ReceiverComponent"</span>/></span><span class="code-tag"></sm:component></span>
<span class="code-tag"><span class="code-comment"><!-- lets subscribe to the output of the foo:jmsReceiver component --></span></span>
- <span class="code-tag"><subscription service=<span class="code-quote">"foo:jmsReceiver"</span> /></span>
-<span class="code-tag"></component></span></pre></div>
+ <span class="code-tag"><sm:subscriptions></span>
+ <span class="code-tag"><sm:subscriptionSpec service=<span class="code-quote">"foo:jmsReceiver"</span> /></span>
+ <span class="code-tag"></sm:subscriptions></span>
+<span class="code-tag"></sm:activationSpec></span></pre></div>
</div>
</p>
<h3><a name="PublishSubscribeRouting-Notes"></a>Notes</h3>
<p>Note that the queue semantics and topic semantics are completely mutually exclusive. A single endpoint can have a collection of destination endpoints used to dispatch messages as well as a group of subscribers.</p>
<p>A message is dispatched to its usual JBI destination endpoint, then whether its dispatched or not, its also dispatched to all of its subscribers.</p>
- <p>To avoid confusing JBI users, it is an error for a message to not be deliverable using the normal JBI sematics. If you wish to allow no message to be dispatched in the normal JBI manner and want to use just subscriber based routing you can disable the JBI error by setting the <b>failIfNoDestinationEndpoint</b> flag on each <b><component/></b>.</p>
+ <p>To avoid confusing JBI users, it is an error for a message to not be deliverable using the normal JBI sematics. If you wish to allow no message to be dispatched in the normal JBI manner and want to use just subscriber based routing you can disable the JBI error by setting the <b>failIfNoDestinationEndpoint</b> flag on each <b><activationSpec/></b>.</p>
<p class="paragraph">
<div class="code">
- <div class="codeContent"><pre class="code-xml"><component id=<span class="code-quote">"jmsReceiver"</span> service=<span class="code-quote">"foo:jmsReceiver"</span>
- failIfNoDestinationEndpoint=<span class="code-quote">"false"</span>
- class=<span class="code-quote">"org.servicemix.components.jms.JmsReceiverComponent"</span>></pre></div>
+ <div class="codeContent"><pre class="code-xml"><sm:activationSpec componentName=<span class="code-quote">"jmsReceiver"</span> service=<span class="code-quote">"foo:jmsReceiver"</span>
+ failIfNoDestinationEndpoint=<span class="code-quote">"false"</span>>
+ <span class="code-tag"><sm:component></span><span class="code-tag"><bean class=<span class="code-quote">"org.apache.servicemix.components.jms.JmsReceiverComponent"</span>></span></pre></div>
</div>
</p>
</div>
Modified: incubator/servicemix/site/Release+Guide
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/Release%2BGuide?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/Release+Guide (original)
+++ incubator/servicemix/site/Release+Guide Mon Feb 27 22:52:24 2006
@@ -222,10 +222,13 @@
<li>Change the version number: <table class="confluenceTable">
<tbody>
<tr>
- <td class="confluenceTd">project.xml</td>
+ <td class="confluenceTd"> project.xml </td>
</tr>
<tr>
- <td class="confluenceTd">etc/project.xml</td>
+ <td class="confluenceTd"> etc/project.xml </td>
+ </tr>
+ <tr>
+ <td class="confluenceTd"> servicemix-assembly/src/main/release/examples/servicemix-web/project.xml </td>
</tr>
</tbody>
</table>
Modified: incubator/servicemix/site/Seda+Flow+MBean
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/Seda%2BFlow%2BMBean?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/Seda+Flow+MBean (original)
+++ incubator/servicemix/site/Seda+Flow+MBean Mon Feb 27 22:52:24 2006
@@ -234,10 +234,34 @@
<th class="confluenceTh"> Description </th>
</tr>
<tr>
- <td class="confluenceTd"> reset </td>
+ <td class="confluenceTd"> start</td>
<td class="confluenceTd"> void </td>
<td class="confluenceTd"> void </td>
- <td class="confluenceTd"> reset all stats counters </td>
+ <td class="confluenceTd"> starts the flow </td>
+ </tr>
+ <tr>
+ <td class="confluenceTd"> stop</td>
+ <td class="confluenceTd"> void </td>
+ <td class="confluenceTd"> void </td>
+ <td class="confluenceTd"> stops the flow </td>
+ </tr>
+ <tr>
+ <td class="confluenceTd"> shutDown</td>
+ <td class="confluenceTd"> void </td>
+ <td class="confluenceTd"> void </td>
+ <td class="confluenceTd"> shutDowns the flow </td>
+ </tr>
+ <tr>
+ <td class="confluenceTd"> onEvent</td>
+ <td class="confluenceTd"> void </td>
+ <td class="confluenceTd"> void </td>
+ <td class="confluenceTd"> Process state changes in Components </td>
+ </tr>
+ <tr>
+ <td class="confluenceTd"> release</td>
+ <td class="confluenceTd"> queue</td>
+ <td class="confluenceTd"> void </td>
+ <td class="confluenceTd"> release a queue </td>
</tr>
</tbody>
</table>
@@ -283,9 +307,7 @@
</tr>
</table>
</p>
- <p>
- <br clear="all">
- </p>
+ <br clear="all">
<h3><a name="SedaFlowMBean-SedaQueueMBean"></a>SedaQueue MBean</h3>
<p>A SedaQueue is used by the Seda style message flow for staging MessageExchanges before they are forwarded to the consuming Component - see <span class="nobr"><a href="http://servicemix/codehaus.org/maven/apidocs/org/servicemix/jbi/nmr/flow/seda/SedaQueue.html" rel="nofollow">SedaQueue java doc</a></span>. A SedaQueue MBean is dervied from <a href="Life+Cycle+MBean" title="Life Cycle MBean">Life Cycle MBean</a>.</p>
<p class="paragraph">
@@ -306,10 +328,10 @@
<th class="confluenceTh"> Description </th>
</tr>
<tr>
- <td class="confluenceTd"> capacity </td>
- <td class="confluenceTd"> int </td>
+ <td class="confluenceTd"> name</td>
+ <td class="confluenceTd"> ComponentNameSpace</td>
<td class="confluenceTd"> read/write </td>
- <td class="confluenceTd"> capacity for MessageExchanges for this queue</td>
+ <td class="confluenceTd"> component name space </td>
</tr>
</tbody>
</table>
Modified: incubator/servicemix/site/ShutDownAssemblyTask
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/ShutDownAssemblyTask?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/ShutDownAssemblyTask (original)
+++ incubator/servicemix/site/ShutDownAssemblyTask Mon Feb 27 22:52:24 2006
@@ -233,7 +233,7 @@
<th class="confluenceTh"> Description </th>
</tr>
<tr>
- <td class="confluenceTd"> assemblyName </td>
+ <td class="confluenceTd"> name </td>
<td class="confluenceTd"> String </td>
<td class="confluenceTd"> the name of the assembly to shutdown </td>
</tr>
@@ -243,6 +243,8 @@
</tr>
</table>
</p>
+ <br>
+ <p class="paragraph"> </p>
</div>
</div>
Modified: incubator/servicemix/site/ShutDownComponentTask
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/ShutDownComponentTask?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/ShutDownComponentTask (original)
+++ incubator/servicemix/site/ShutDownComponentTask Mon Feb 27 22:52:24 2006
@@ -233,7 +233,7 @@
<th class="confluenceTh"> Description </th>
</tr>
<tr>
- <td class="confluenceTd"> componentName </td>
+ <td class="confluenceTd"> name </td>
<td class="confluenceTd"> String </td>
<td class="confluenceTd"> the name of the Component to shutdown </td>
</tr>
@@ -243,6 +243,8 @@
</tr>
</table>
</p>
+ <br>
+ <p class="paragraph"> </p>
</div>
</div>
Modified: incubator/servicemix/site/StartAssemblyTask
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/StartAssemblyTask?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/StartAssemblyTask (original)
+++ incubator/servicemix/site/StartAssemblyTask Mon Feb 27 22:52:24 2006
@@ -233,7 +233,7 @@
<th class="confluenceTh"> Description </th>
</tr>
<tr>
- <td class="confluenceTd"> assemblyName </td>
+ <td class="confluenceTd"> name </td>
<td class="confluenceTd"> String </td>
<td class="confluenceTd"> the name of the assembly to start </td>
</tr>
@@ -243,6 +243,8 @@
</tr>
</table>
</p>
+ <br>
+ <p class="paragraph"> </p>
</div>
</div>
Modified: incubator/servicemix/site/StartComponentTask
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/StartComponentTask?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/StartComponentTask (original)
+++ incubator/servicemix/site/StartComponentTask Mon Feb 27 22:52:24 2006
@@ -214,7 +214,7 @@
<div>
<div id="Content">
- <p>The StartAssemblyTask starts a Component <span class="nobr"><a href="http://servicemix.org/maven/servicemix-core/apidocs/org/apache/servicemix/jbi/management/task/StartComponentTask.html" rel="nofollow">StartAssemblyTask </a></span><br clear="all">
+ <p>The StartAssemblyTask starts a Component <span class="nobr"><a href="http://servicemix.org/maven/servicemix-core/apidocs/org/apache/servicemix/jbi/management/task/StartComponentTask.html" rel="nofollow">StartComponentTask </a></span><br clear="all">
</p>
<p class="paragraph">
<table align="center" border=0 cellpadding=5 cellspacing="8px" class="infoMacro" width="85%">
@@ -233,7 +233,7 @@
<th class="confluenceTh"> Description </th>
</tr>
<tr>
- <td class="confluenceTd"> componentName </td>
+ <td class="confluenceTd"> name </td>
<td class="confluenceTd"> String </td>
<td class="confluenceTd"> the name of the Component to start </td>
</tr>
@@ -243,6 +243,8 @@
</tr>
</table>
</p>
+ <br>
+ <p class="paragraph"> </p>
</div>
</div>
Modified: incubator/servicemix/site/StopAssemblyTask
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/StopAssemblyTask?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/StopAssemblyTask (original)
+++ incubator/servicemix/site/StopAssemblyTask Mon Feb 27 22:52:24 2006
@@ -233,7 +233,7 @@
<th class="confluenceTh"> Description </th>
</tr>
<tr>
- <td class="confluenceTd"> assemblyName </td>
+ <td class="confluenceTd"> name </td>
<td class="confluenceTd"> String </td>
<td class="confluenceTd"> the name of the assembly to stop </td>
</tr>
@@ -243,6 +243,8 @@
</tr>
</table>
</p>
+ <br>
+ <p class="paragraph"> </p>
</div>
</div>
Modified: incubator/servicemix/site/StopComponentTask
URL: http://svn.apache.org/viewcvs/incubator/servicemix/site/StopComponentTask?rev=381583&r1=381582&r2=381583&view=diff
==============================================================================
--- incubator/servicemix/site/StopComponentTask (original)
+++ incubator/servicemix/site/StopComponentTask Mon Feb 27 22:52:24 2006
@@ -233,7 +233,7 @@
<th class="confluenceTh"> Description </th>
</tr>
<tr>
- <td class="confluenceTd"> componentName </td>
+ <td class="confluenceTd"> name </td>
<td class="confluenceTd"> String </td>
<td class="confluenceTd"> the name of the Component to stop </td>
</tr>
@@ -243,6 +243,8 @@
</tr>
</table>
</p>
+ <br>
+ <p class="paragraph"> </p>
</div>
</div>