svn commit: r669249 - in /synapse/trunk/java/src/site/xdoc: Synapse_Extending.xml Synapse_Samples_Setup.xml

[ve...@apache.org]

Author: veithen
Date: Wed Jun 18 11:26:15 2008
New Revision: 669249

URL: http://svn.apache.org/viewvc?rev=669249&view=rev
Log:
Some slight documentation improvements

Modified:
    synapse/trunk/java/src/site/xdoc/Synapse_Extending.xml
    synapse/trunk/java/src/site/xdoc/Synapse_Samples_Setup.xml

Modified: synapse/trunk/java/src/site/xdoc/Synapse_Extending.xml
URL: http://svn.apache.org/viewvc/synapse/trunk/java/src/site/xdoc/Synapse_Extending.xml?rev=669249&r1=669248&r2=669249&view=diff
==============================================================================
--- synapse/trunk/java/src/site/xdoc/Synapse_Extending.xml (original)
+++ synapse/trunk/java/src/site/xdoc/Synapse_Extending.xml Wed Jun 18 11:26:15 2008
@@ -121,10 +121,12 @@
       through the chain of mediators, for each and every message received and
       processed by Synapse. Each message instance is wrapped within a
       MessageContext instance, and the message context is set with the
-      references to the SynapseConfiguration and SynapseEnvironments. The
-      SynapseConfiguration holds the global configuration model that defines
+      references to the SynapseConfiguration and SynapseEnvironment objects. The
+      <a href="apidocs/org/apache/synapse/config/SynapseConfiguration.html">SynapseConfiguration</a>
+      object holds the global configuration model that defines
       mediation rules, local registry entries and other and configuration, while
-      the environment gives access to the underlying SOAP implementation used -
+      the <a href="apidocs/org/apache/synapse/core/SynapseEnvironment.html">SynapseEnvironment</a>
+      object gives access to the underlying SOAP implementation used -
       Axis2. A typical mediator would need to manipulate the MessageContext by
       referring to the SynapseConfiguration. However it is strongly recommended
       that the SynapseConfiguration is not updated by mediator instances as it
@@ -212,8 +214,8 @@
 
 }</pre>
     <p>
-      The MessageContext interface is based on the Axis2 <a>MessageContext</a>
-      interface, and uses the Axis2 <a>EndpointReference</a> and
+      The MessageContext interface is based on the Axis2 MessageContext
+      interface, and uses the Axis2 EndpointReference and
       SOAPEnvelope classes/interfaces. The purpose of this interface is to
       capture a message as it flows through the system. As you will see the
       message payload is represented using the SOAP infoset. Binary messages can
@@ -257,7 +259,7 @@
     public String getType();
 }</pre>
     <p>
-      A mediator can read and/or modify the <a>SynapseMessage</a> in
+      A mediator can read and/or modify the message encapsulated in the MessageContext in
       any suitable manner - adjusting the routing headers or changing the
       message body. If the mediate() method returns false, it signals to the
       Synapse processing model to stop further processing of the message. For
@@ -273,7 +275,7 @@
       Mediators may be Node mediators (i.e. these that can contain child
       mediators) or Leaf mediators (mediators that does not hold any other child
       mediators). A Node mediator  must implement the
-      org.apache.synapse.api.ListMediator interface listed below, or extend from
+      org.apache.synapse.mediators.ListMediator interface listed below, or extend from
       the org.apache.synapse.mediators.AbstractListMediator.
     </p>
     <h4>

Modified: synapse/trunk/java/src/site/xdoc/Synapse_Samples_Setup.xml
URL: http://svn.apache.org/viewvc/synapse/trunk/java/src/site/xdoc/Synapse_Samples_Setup.xml?rev=669249&r1=669248&r2=669249&view=diff
==============================================================================
--- synapse/trunk/java/src/site/xdoc/Synapse_Samples_Setup.xml (original)
+++ synapse/trunk/java/src/site/xdoc/Synapse_Samples_Setup.xml Wed Jun 18 11:26:15 2008
@@ -750,10 +750,10 @@
 <div>
 <p>Definition of the reusable database connection pool or datasources can be
 done using synapse.properties file. It is possible to configure any number of
-datasources. Currently only supports two type of datasources and those are
-based on apache dbcp datasources. Those types are BasicDataSource and
-PerUserPoolDataSource (based on apache dhcp).Following configuration includes
-both two definition. This configuration is related with sample 363.</p>
+datasources. Currently only two types of datasources are supported and those are
+based on <a href="http://commons.apache.org/dbcp/">Apache DBCP</a> datasources: BasicDataSource and
+PerUserPoolDataSource. Following configuration includes
+both two definitions. This configuration is related with sample 363.</p>
 
 
 <p>Configuration is somewhat similar to the log4j appender configuration.</p>