Author: ruwan Date: Tue Jul 7 11:37:31 2009 New Revision: 40974 URL: http://wso2.org/svn/browse/wso2?view=rev&revision=40974
Log: Fixing the documentation Modified: branches/esb/java/2.1/product/docs/resources/images/esb-architecture.png branches/esb/java/2.1/product/docs/resources/images/synapse-flow.png branches/esb/java/2.1/product/docs/xdoc/configuration_language.xml branches/esb/java/2.1/product/docs/xdoc/index.xml branches/esb/java/2.1/product/docs/xdoc/user_guide.xml Modified: branches/esb/java/2.1/product/docs/resources/images/esb-architecture.png URL: http://wso2.org/svn/browse/wso2/branches/esb/java/2.1/product/docs/resources/images/esb-architecture.png?rev=40974&r1=40973&r2=40974&view=diff ============================================================================== Binary files. No diff available. Modified: branches/esb/java/2.1/product/docs/resources/images/synapse-flow.png URL: http://wso2.org/svn/browse/wso2/branches/esb/java/2.1/product/docs/resources/images/synapse-flow.png?rev=40974&r1=40973&r2=40974&view=diff ============================================================================== Binary files. No diff available. Modified: branches/esb/java/2.1/product/docs/xdoc/configuration_language.xml URL: http://wso2.org/svn/browse/wso2/branches/esb/java/2.1/product/docs/xdoc/configuration_language.xml?rev=40974&r1=40973&r2=40974&view=diff ============================================================================== --- branches/esb/java/2.1/product/docs/xdoc/configuration_language.xml (original) +++ branches/esb/java/2.1/product/docs/xdoc/configuration_language.xml Tue Jul 7 11:37:31 2009 @@ -26,121 +26,8 @@ <title> WSO2 ESB - Configuration Language </title> - <link href="css/esb-docs.css" rel="stylesheet" /> - <style type="text/css"> - .command { - border: 1px dashed #3c78b5; - text-align: left; - background-color: #f0f0f0; - padding: 3px; - font-size: 11px; - font-family: Courier; - margin: 10px; - line-height: 13px; - } - .consoleOutput { - border: 1px dashed #3c78b5; - font-size: 11px; - font-family: Courier; - margin: 10px; - line-height: 13px; - background-color: #f0f0f0; - border-bottom: 1px dashed #3c78b5; - padding: 3px; - border-style: solid; - } - .info { - border-style: solid; - border-width: 1px; - border-color: #090; - background-color: #dfd; - text-align:left; - margin-top: 5px; - margin-bottom: 5px; - } - li { - font-family: Verdana, arial, sans-serif; - font-size: 11px; - line-height: 16px; - color: #000000; - font-weight: normal; - } - p { - font-family: Verdana, arial, sans-serif; - font-size: 11px; - line-height: 16px; - color: #000000; - font-weight: normal; - } - pre { - padding: 0px; - margin-top: 5px; - margin-left: 15px; - margin-bottom: 5px; - margin-right: 5px; - text-align: left; - background-color: #f0f0f0; - padding: 3px; - border: 1px dashed #3c78b5; - font-size: 11px; - font-family: Courier; - margin: 10px; - line-height: 13px; - } - h1 { - font-size: 24px; - line-height: normal; - font-weight: bold; - background-color: #f0f0f0; - color: #003366; - border-bottom: 1px solid #3c78b5; - padding: 2px; - margin: 36px 0px 4px 0px; - } - h2 { - font-size: 18px; - line-height: normal; - font-weight: bold; - background-color: #f0f0f0; - border-bottom: 1px solid #3c78b5; - padding: 2px; - margin: 27px 0px 4px 0px; - } - h3 { - font-size: 14px; - line-height: normal; - font-weight: bold; - background-color: #f0f0f0; - padding: 2px; - margin: 21px 0px 4px 0px; - } - h4 { - font-size: 12px; - line-height: normal; - font-weight: bold; - background-color: #f0f0f0; - padding: 2px; - margin: 18px 0px 4px 0px; - } - .data-table{ - font-family:Verdana,Arial,Helvetica,sans-serif; - font-size:11px; - border:0px; - margin:0px; - border:solid 1px #cdcdcd; - } - .data-table th{ - background-color:#eeeeee; - border-bottom:solid 1px #8d8d8d; - padding-top:5px; - padding-left:3px; - text-align:left; - } - .data-table td{ - padding-top:4px; - padding-left:3px; - border-bottom:solid 1px #e1e1e1; - }</style> + <link href="css/esb-docs.css" rel="stylesheet"/> + <link href="styles/dist-docs.css" rel="stylesheet" type="text/css" media="all"/> </head> <body> @@ -195,8 +82,7 @@ configured to return a custom message or a fault to the requesting client without forwarding the request to the actual service. </p> -<p><img alt="Synapse message flow" src="images/synapse-flow.png" width="400" -height="300" /> </p> +<p><img alt="Synapse message flow" src="images/synapse-flow.png" width="800px" /> </p> <p>The Synapse ESB can operate in two modes: </p> @@ -340,7 +226,7 @@ <definitions> element would be treated as the "main" sequence, if a named sequence with the name "main" cannot be found. </p> -<h2><a id="registry">Registry</a> </h2> +<h2 id="registry">Registry</h2> <p>The <registry> element is used to define the remote registry used by the configuration. The registry provider specifies an implementation class for @@ -375,7 +261,7 @@ different resources, or mark some resources as never expires. (e.g. Check the WSO2 ESB implementation built over the Apache Synapse ESB core) </p> -<h3><a id="localEntry">Local Registry / Local Entry</a> </h3> +<h3 id="localEntry">Local Registry / Local Entry</h3> <p>The <localEntry> element is used to declare registry entries that are local to the Synapse instance, as shown below </p> @@ -398,7 +284,7 @@ </localEntry> <localEntry key="xslt-key-req" src="file:repository/conf/sample/resources/transform/transform.xslt"/></pre> -<h2><a id="sequence">Sequences</a> </h2> +<h2 id="sequence">Sequences</h2> <p>A <sequence> element is used to define a sequence of mediators that can be invoked later by name. The sequences named "main" and "fault" has @@ -433,7 +319,7 @@ .. </sequence></pre> -<h2><a id="endpoint">Endpoints</a> </h2> +<h2 id="endpoint">Endpoints</h2> <p>An <endpoint> element defines a destination for an outgoing message. An endpoint may be specified as an address endpoint, WSDL based endpoint, a @@ -453,7 +339,7 @@ log4j.properties file. Setting the trace log level to TRACE will dump detailed trace information including message payloads. </p> -<h4><a id="address-endpoint">Address Endpoint</a> </h4> +<h3 id="address-endpoint">Address Endpoint</h3> <p>Address endpoint is an endpoint defined by specifying the EPR and other attributes of the endpoint directly in the configuration. The 'uri' attribute @@ -549,11 +435,11 @@ <td><tt>vfs:file:///home/user/directory</tt></td> </tr> <tr> - <td></td> + <td/> <td><tt>vfs:file:///home/user/file</tt></td> </tr> <tr> - <td></td> + <td/> <td><tt>vfs:ftp://guest:gu...@localhost/directory?vfs.passive=true</tt></td> </tr> <tr> @@ -563,7 +449,7 @@ </tbody> </table> -<h4><a id="default-endpoint">Default Endpoint</a> </h4> +<h3 id="default-endpoint">Default Endpoint</h3> <p>Default endpoint is an endpoint defined for adding QoS and other configurations to the endpoint which is resolved from the 'To' address of the @@ -590,7 +476,7 @@ </suspendDurationOnFailure>? </default></pre> -<h4><a id="wsdl-endpoint">WSDL Endpoint</a> </h4> +<h3 id="wsdl-endpoint">WSDL Endpoint</h3> <p>WSDL endpoint is an endpoint definition based on a specified WSDL document. The WSDL document can be specified either as a URI or as an inlined definition @@ -625,7 +511,7 @@ </timeout>? </wsdl></pre> -<h4><a id="load-balanced-endpoint">Load balanced Endpoint</a> </h4> +<h3 id="load-balanced-endpoint">Load balanced Endpoint</h3> <p>A Load balanced endpoint distributes the messages (load) arriving at it among a set of listed endpoints by evaluating the load balancing policy and any @@ -656,7 +542,7 @@ <endpoint .../>+ </loadBalance></pre> -<h4><a id="fail-over-endpoint">Failover Endpoint</a> </h4> +<h3 id="fail-over-endpoint">Failover Endpoint</h3> <p>Failover endpoints send messages to the listed endpoints with the following failover behavior. At the start, the first listed endpoint is selected as the @@ -669,7 +555,7 @@ <endpoint .../>+ </failover></pre> -<h2><a id="proxy">Proxy service</a> </h2> +<h2 id="proxy">Proxy service</h2> <p>A <proxy> element is used to define a Synapse Proxy service. </p> <pre xml:space="preserve"> <proxy name="string" [transports="(http |https |jms |.. )+|all"] [pinnedServers="(serverName )+"]> @@ -748,7 +634,7 @@ <table border="1" cellpadding="0" cellspacing="0" style="width: 100%" class="data-table"> - <caption></caption> + <caption>Service Parameters</caption> <tbody> <tr> <th>Parameter </th> @@ -776,7 +662,7 @@ <table border="1" cellpadding="0" cellspacing="0" style="width: 100%" class="data-table"> - <caption></caption> + <caption>Transport specific parameters</caption> <tbody> <tr> <th>Transport </th> @@ -792,25 +678,25 @@ listen for messages for this service </td> </tr> <tr> - <td></td> + <td/> <td>Optional </td> <td>transport.jms.Destination </td> <td>The JMS destination name (Defaults to the service name) </td> </tr> <tr> - <td></td> + <td/> <td>Optional </td> <td>transport.jms.DestinationType </td> <td>The JMS destination type. Accept values 'queue' or 'topic' </td> </tr> <tr> - <td></td> + <td/> <td>Optional </td> <td>transport.jms.ReplyDestination </td> <td>The destination where a reply will be posted </td> </tr> <tr> - <td></td> + <td/> <td>Optional </td> <td>transport.jms.Wrapper </td> <td>The wrapper element for the JMS message </td> @@ -823,7 +709,7 @@ this service </td> </tr> <tr> - <td></td> + <td/> <td>Required </td> <td>transport.vfs.ContentType </td> <td>The expected content type for files retrieved for this service. The @@ -838,70 +724,70 @@ </td> </tr> <tr> - <td></td> + <td/> <td>Optional </td> <td>transport.vfs.FileNamePattern </td> <td>A file name regex pattern to match files against a directory specified by the FileURI </td> </tr> <tr> - <td></td> + <td/> <td>Optional </td> <td>transport.PollInterval </td> <td>The poll interval (in seconds) </td> </tr> <tr> - <td></td> + <td/> <td>Optional </td> <td>transport.vfs.ActionAfterProcess </td> <td>DELETE or MOVE </td> </tr> <tr> - <td></td> + <td/> <td>Optional </td> <td>transport.vfs.MoveAfterProcess </td> <td>The directory to move files after processing (i.e. all files process successfully) </td> </tr> <tr> - <td></td> + <td/> <td>Optional </td> <td>transport.vfs.ActionAfterErrors </td> <td>DELETE or MOVE </td> </tr> <tr> - <td></td> + <td/> <td>Optional </td> <td>transport.vfs.MoveAfterErrors </td> <td>The directory to move files after errors (i.e. some of the files succeed but some fail) </td> </tr> <tr> - <td></td> + <td/> <td>Optional </td> <td>transport.vfs.ActionAfterFailure </td> <td>DELETE or MOVE </td> </tr> <tr> - <td></td> + <td/> <td>Optional </td> <td>transport.vfs.MoveAfterFailure </td> <td>The directory to move after failure (i.e. all files fail) </td> </tr> <tr> - <td></td> + <td/> <td>Optional </td> <td>transport.vfs.ReplyFileURI </td> <td>Reply file URI </td> </tr> <tr> - <td></td> + <td/> <td>Optional </td> <td>transport.vfs.ReplyFileName </td> <td>Reply file name (defaults to response.xml) </td> </tr> <tr> - <td></td> + <td/> <td>Optional </td> <td>transport.vfs.MoveTimestampFormat </td> <td>Timestamp prefix format for processed file name. @@ -919,7 +805,7 @@ jar:zip:outer.zip!/nested.jar!/somedir ftp://myusername:mypassw...@somehost/pub/downloads/somefile.tgz[?vfs.passive=true]</pre> -<h2><a id="task">Tasks</a> </h2> +<h2 id="task">Scheduled Tasks</h2> <p>A <task> element is used to define a Synapse Startup Task. </p> @@ -955,7 +841,7 @@ started using pinnedServers attribute. Refer to the explanation of this attribute under proxy services for more information. </p> -<h2><a id="mediator">Mediators</a> </h2> +<h2 id="mediator">Mediators</h2> <p>A mediator token refers to any of the following tokens: </p> @@ -970,9 +856,9 @@ allows Apache BSF scripts such as Javascript, Ruby, Groovy etc to be used for mediation. </p> -<h3>Core Mediators </h3> +<h2>Core Mediators</h2> -<h4><a id="send">Send</a> </h4> +<h3 id="send">Send</h3> <p>The send token represents a <send> element, used to send messages out of Synapse to some endpoint. The send mediator also copies any message context @@ -1011,7 +897,7 @@ <p>and the endpoint token refers to an anonymous endpoint definition. </p> -<h4><a id="drop">Drop</a> </h4> +<h3 id="drop">Drop</h3> <p>The drop token refers to a <drop> element which is used to stop further processing of a message: </p> @@ -1021,7 +907,7 @@ <p>Once the <drop> mediator executes, further processing of the current message stops. A the drop mediator does not necessarily close transports. </p> -<h4><a id="log">Log</a> </h4> +<h3 id="log">Log</h3> <p>The log token refers to a <log> element which may be used to log messages being mediated: </p> @@ -1047,7 +933,7 @@ <p>A separator if defined will be used to separate the attributes being logged. The default separator is the ',' comma. </p> -<h4><a id="property">Property</a> </h4> +<h3 id="property">Property</h3> <pre xml:space="preserve"> <property name="string" [action=set|remove] (value="literal" | expression="xpath") [scope=transport|axis2|axis2-client]/></pre> @@ -1157,14 +1043,14 @@ 'Content-Type' transport header, which is going to be the Content-Type of the current message </li></ul> -<h4><a id="sequence_ref">Sequence</a> </h4> +<h3 id="sequence_ref">Sequence</h3> <pre xml:space="preserve"> <sequence key="name"/></pre> <p>A sequence ref token refers to a <sequence> element which is used to invoke a named sequence of mediators. </p> -<h4><a id="validate">Validate</a> </h4> +<h3 id="validate">Validate</h3> <pre xml:space="preserve"> <validate [source="xpath"]> <property name="validation-feature-id" value="true|false"/>* @@ -1183,9 +1069,9 @@ href="http://xerces.apache.org/xerces2-j/features.html";>http://xerces.apache.org/xerces2-j/features.html</a>) </p> -<h3>Transformation Mediators </h3> +<h2>Transformation Mediators</h2> -<h4><a id="fault">Fault</a> </h4> +<h3 id="fault">Fault</h3> <pre xml:space="preserve"> <makefault [version="soap11|soap12|pox"]> <code (value="literal" | expression="xpath")/> @@ -1202,7 +1088,7 @@ message. If a 'version' attribute is specified, the created fault message will be created as a selected SOAP 1.1, SOAP 1.2 or POX fault. </p> -<h4><a id="callout">Callout</a> </h4> +<h3 id="callout">Callout</h3> <pre xml:space="preserve"> <callout serviceURL="string" [action="string"]> <configuration [axis2xml="string"] [repository="string"]/>? <source xpath="expression" | key="string"> @@ -1224,7 +1110,7 @@ and samples/axis2Client/client_repo as the client repository unless these are specified separately </p> -<h4><a id="xslt">XSLT</a> </h4> +<h3 id="xslt">XSLT</h3> <pre xml:space="preserve"> <xslt key="string" [source="xpath"]> <property name="string" (value="literal" | expression="xpath")/>* @@ -1247,7 +1133,7 @@ includes from the repository. It works in exactly the same way as the corresponding element in a <proxy> definition. </p> -<h4><a id="xquery">XQuery</a> </h4> +<h3 id="xquery">XQuery</h3> <pre xml:space="preserve"><xquery key="string" [target="xpath"]> <variable name="string" type="string" [key="string"] [expression="xpath"] [value="string"]/>? </xquery> </pre> @@ -1283,7 +1169,7 @@ <li>XQItemType.XQITEMKIND_ELEMENT -> ELEMENT </li> </ul> -<h4><a id="header">Header</a> </h4> +<h3 id="header">Header</h3> <pre xml:space="preserve"> <header name="qname" (value="literal" | expression="xpath") [action="set"]/> <header name="qname" action="remove"/></pre> @@ -1295,9 +1181,9 @@ attribute specifies whether the mediator should set or remove the header. If omitted, it defaults to a set-header. </p> -<h3>Selection Mediators </h3> +<h2>Selection Mediators </h2> -<h4><a id="filter">Filter</a> </h4> +<h3 id="filter">Filter</h3> <pre xml:space="preserve"> <filter (source="xpath" regex="string") | xpath="xpath"> mediator+ @@ -1324,7 +1210,7 @@ element in sequence, while failed messages will be mediated using the set of mediators enclosed in the else element in sequence </p> -<h4><a id="switch">Switch</a> </h4> +<h3 id="switch">Switch</h3> <pre xml:space="preserve"> <switch source="xpath"> <case regex="string"> @@ -1340,9 +1226,9 @@ the specified cases does not match and a default case exists, it will be executed. </p> -<p><a id="in"/> </p> +<h3 id="in"/> -<h4><a id="out">In / Out</a> </h4> +<h3 id="out">In/Out</h3> <pre xml:space="preserve"><in><br /> mediator+ </in><br /></pre> @@ -1359,7 +1245,7 @@ incoming messages would pass through the "<in>" mediators and vice versa. </p> -<h4><a id="router">Router</a> </h4> +<h3 id="router">Router</h3> <pre xml:space="preserve"><router [continueAfter=(true | false)]> <route expression="xpath" [match="regEx"] [breakRouter=(true | false)]> <target [sequence="string"] [endpoint="string"]> @@ -1393,9 +1279,9 @@ inline sequence and a refered sequence at the same time. The same applies to endpoit of the target as well. </p> -<h3>Database Mediators </h3> +<h2>Database Mediators</h2> -<h4><a id="dblookup">DB-lookup</a> </h4> +<h3 id="dblookup">DB-lookup</h3> <pre xml:space="preserve"><dblookup> <connection> @@ -1457,7 +1343,7 @@ defines the name under which the result is stored in the Synapse message context, and the column attribute specifies a column number or name . </p> -<h4><a id="dbreport">DB-report</a> </h4> +<h3 id="dbreport">DB-report</h3> <pre xml:space="preserve"><dbreport> <connection> @@ -1486,9 +1372,9 @@ <p>The dbreport mediator is very similar to the dblookup mediator, but writes information to a Database, using the specified insert SQL statement.</p> -<h3>Advanced Mediators </h3> +<h2>Advanced Mediators</h2> -<h4><a id="RMSequence">RMSequence</a> </h4> +<h3 id="RMSequence">RMSequence</h3> <pre xml:space="preserve"> <RMSequence (correlation="xpath" [last-message="xpath"]) | single="true" [version="1.0|1.1"]/></pre> @@ -1505,7 +1391,7 @@ attribute the WS-RM specification version to be used can be specified, 1.0 or 1.1. </p> -<h4><a id="throttle">Throttle</a> </h4> +<h3 id="throttle">Throttle</h3> <pre xml:space="preserve"><throttle [onReject="string"] [onAccept="string"] id="string"> (<policy key="string"/> | <policy>..</policy>) @@ -1525,7 +1411,7 @@ 'onAccept' sequence references or inline sequences define how accepted and rejected messages are to be handled. </p> -<h4><a id="cache">Cache</a> </h4> +<h3 id="cache">Cache</h3> <pre xml:space="preserve"> <cache [id="string"] [hashGenerator="class"] [timeout="seconds"] [scope=(per-host | per-mediator)] collector=(true | false) [maxMessageSize="in-bytes"]> @@ -1554,7 +1440,7 @@ element may define if the cache is disk or memory based, and the 'maxSize' attribute defines the maximum number of elements to be cached. </p> -<h4><a id="clone">Clone</a> </h4> +<h3 id="clone">Clone</h3> <pre xml:space="preserve"> <clone [continueParent=(true | false)]> <target [to="uri"] [soapAction="qname"] [sequence="sequence_ref"] [endpoint="endpoint_ref"]> @@ -1573,7 +1459,7 @@ the boolean value of the optional 'continueParent' attribute. Optionally a custom 'To' address and/or a 'Action' may be specified for cloned messages </p> -<h4><a id="iterate">Iterate</a> </h4> +<h3 id="iterate">Iterate</h3> <pre xml:space="preserve"> <iterate [continueParent=(true | false)] [preservePayload=(true | false)] (attachPath="xpath")? expression="xpath"> <target [to="uri"] [soapAction="qname"] [sequence="sequence_ref"] [endpoint="endpoint_ref"]> @@ -1596,7 +1482,7 @@ creating the splitted messages, and defaults to 'false', in which case the splitted messages would contain the split elements as the SOAP body. </p> -<h4><a id="aggregate">Aggregate</a> </h4> +<h3 id="aggregate">Aggregate</h3> <pre xml:space="preserve"> <aggregate> <correlateOn expression="xpath"/>? @@ -1621,7 +1507,7 @@ expression specified by the attribute 'expression' on the 'onComplete' element. </p> -<h4><a id="event">Event</a> </h4> +<h3 id="event">Event</h3> <pre xml:space="preserve"> <syn:eventPublisher eventSourceName="event-source-name"/></pre> @@ -1629,7 +1515,7 @@ presence of defined event sources are necessary prior to the usage of this mediator. </p> -<h4><a id="transaction">Transaction</a> </h4> +<h3 id="transaction">Transaction</h3> <pre xml:space="preserve"> <syn:transaction action="transaction-action" /></pre> @@ -1641,9 +1527,9 @@ later. Additionally, the transaction mediator supports three other actions, i.e. use-existing-or-new, fault-if-no-tx, rollback. </p> -<h3>Extension mediators </h3> +<h2>Extension mediators</h2> -<h4><a id="class">Class</a> </h4> +<h3 id="class">Class</h3> <pre xml:space="preserve"> <class name="class-name"> <property name="string" value="literal"> @@ -1656,7 +1542,7 @@ interface. If any properties are specified, the corresponding setter methods are invoked on the class, once, during initialization. </p> -<h4><a id="pojoCommand">POJOCommand</a> </h4> +<h3 id="pojoCommand">POJOCommand</h3> <pre xml:space="preserve"> <pojoCommand name="class-name"> ( @@ -1680,7 +1566,7 @@ behaviour is expected or not via the Read, Update and ReadAndUpdate properties. </p> -<h3><a id="script">Scripting language mediators</a> </h3> +<h2 id="script">Scripting language mediators</h2> <p>Synapse supports Mediators implemented in a variety of scripting languages such as JavaScript, Python or Ruby. There are two ways of defining script @@ -1731,13 +1617,13 @@ getPayloadXML and setPayloadXML, E4X XML objects, and when using Ruby, REXML documents. </p> -<h3>Extensibility of Synapse </h3> +<h2>Extensibility of Synapse </h2> <p>The Synapse configuration language could be easily extended, with configuration extensions as well as mediation extensions. The Spring mediator is such an example. </p> -<h4>Spring Configuration </h4> +<h3>Spring Configuration</h3> <p>A Spring configuration could be created as a localEntry or remote registry entry providing a URL or a key reference to a Registry. The configuration is @@ -1750,7 +1636,7 @@ <p>The name attribute specifies a unique name for the configuration, and the src, key or inlined XML references to the Spring configuration </p> -<h4><a id="spring">Spring mediator</a> </h4> +<h3 id="spring">Spring mediator</h3> <pre xml:space="preserve"> <spring:spring bean="exampleBean1" key="string"/></pre> @@ -1764,7 +1650,7 @@ it to act as a Mediator. The key will reference the Spring ApplicationContext/Configuration used for the bean </p> -<h4><a id="spring1">Rule Mediator - Java Rule mediator </a></h4> +<h3 id="spring1">Rule Mediator - Java Rule mediator</h3> <p>Rule mediator has been implemented based on <strong>Java Rule Engine API JSR-94</strong>. This provides the capability required for mediation using Modified: branches/esb/java/2.1/product/docs/xdoc/index.xml URL: http://wso2.org/svn/browse/wso2/branches/esb/java/2.1/product/docs/xdoc/index.xml?rev=40974&r1=40973&r2=40974&view=diff ============================================================================== --- branches/esb/java/2.1/product/docs/xdoc/index.xml (original) +++ branches/esb/java/2.1/product/docs/xdoc/index.xml Tue Jul 7 11:37:31 2009 @@ -83,7 +83,7 @@ </ol> <h2>WSO2 ESB Component Architecture</h2> - <div style="float:left;padding-right:20px;padding-bottom:10px;padding-top:20px;"><img src="images/esb-architecture.png" alt="ESB Architecture" style="float:left;"/></div> + <div style="float:left;padding-right:20px;padding-bottom:10px;padding-top:20px;"><img src="images/esb-architecture.png" alt="ESB Architecture" /></div> <p>WSO2 ESB supports all the widely used transports including HTTP/s, JMS, VFS and domain specific transports like FIX, HL7 and so on.. A new transport can be added easily using Modified: branches/esb/java/2.1/product/docs/xdoc/user_guide.xml URL: http://wso2.org/svn/browse/wso2/branches/esb/java/2.1/product/docs/xdoc/user_guide.xml?rev=40974&r1=40973&r2=40974&view=diff ============================================================================== --- branches/esb/java/2.1/product/docs/xdoc/user_guide.xml (original) +++ branches/esb/java/2.1/product/docs/xdoc/user_guide.xml Tue Jul 7 11:37:31 2009 @@ -397,9 +397,9 @@ specified endpoints. In addition, scheduled tasks may inject new messages into the ESB periodically or execute other tasks. </p> - <h3 id="Proxy"> + <h2 id="Proxy"> Proxy Services - </h3> + </h2> <p> Proxy services define virtual services hosted on the ESB that can accept requests, mediate them, and deliver them to an actual service. Proxy @@ -408,16 +408,16 @@ aspects like WS-RM, WS-Security, etc. </p> <p/> - <h4 id="addProxy"> + <h3 id="addProxy"> Adding a Proxy Service - </h4> + </h3> <p> This function allows you to add a proxy service. Please refer <a href="proxyservices/docs/userguide.html">Adding a Proxy Service</a> for details. </p> - <h4 id="proxyActions"> + <h3 id="proxyActions"> Proxy Service Actions - </h4> + </h3> <p> You can edit, delete, enable statistics, start and stop the proxy service, and enable tracing for the proxy service as described below. All existing @@ -492,9 +492,9 @@ </ul> </blockquote> <p/> - <h3 id="Task"> + <h2 id="Task"> Scheduled Tasks - </h3> + </h2> <p> The built-in Quartz scheduler lets administrators schedule tasks to run at specified intervals. Tasks may be used to initiate long-running tasks, @@ -509,9 +509,9 @@ Please refer the <a href="user_guide.html"> documentation</a> on scheduled tasks for details. </p> - <h3 id="Endpoints"> + <h2 id="Endpoints"> Endpoints - </h3> + </h2> <p> An endpoint is a specific destination for a message. It may be specified as an Address endpoint, WSDL endpoint, a Failover group, or a Loadbalance @@ -525,9 +525,9 @@ Please refer the <a href="endpoints/docs/userguide.html">documentation</a> on endpoints for details. </p> - <h3 id="Sequences"> + <h2 id="Sequences"> Sequences - </h3> + </h2> <p> A sequence element is used to define a sequence of mediators that can be invoked later as a sequence. If the configuration defines a sequence named @@ -541,9 +541,9 @@ Please refer the <a href="sequences/docs/userguide.html">documentation</a> on managing sequences for details. </p> - <h3 id="Local"> + <h2 id="Local"> Local Registry Entries - </h3> + </h2> <p> The local registry entries are used to locally define resources such as scripts, schemas, WSDLs, policies and other resources in a configuration. @@ -551,9 +551,9 @@ static. An entry that exists in the local registry has higher precedence over an entry with the same name that exists in the integrated registry. </p> - <h4 id="Local1"> + <h3 id="Local1"> Adding a Local Registry Entry - </h4> + </h3> <ol> <li> Click <strong>Local Entries</strong> on the navigator. @@ -619,9 +619,9 @@ </li> </ol> </blockquote> - <h4 id="Registry"> + <h3 id="Registry"> Local Registry Actions - </h4> + </h3> <p> You can edit and delete previously entered local registry entries. All existing local registry entries will be displayed in the Registry Entries @@ -664,9 +664,9 @@ </li> </ul> </blockquote> - <h3 id="Configurat"> + <h2 id="Configurat"> Synapse Configuration - </h3> + </h2> <p> This function commits the configuration changes you made to the local storage of the host running the ESB. The XML code for your configuration @@ -712,15 +712,15 @@ target endpoints for the proxy services. </p> <p/> - <h4 id="Manage"> + <h3 id="Manage"> Manage Registry Entry - </h4> + </h3> <p>Please refer the <a href="resources/docs/userguide.html">documentation</a> on managing the embeded registry for details.</p> <hr/> - <h2 id="Monitoring"> + <h3 id="Monitoring"> Monitoring the System - </h2> + </h3> <p> This feature provides information about the ESB on the Administrator Console. It displays <a href="statistics/docs/userguide.html">system statistics</a>, _______________________________________________ Esb-java-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
