Author: saliya Date: Tue Feb 3 01:51:20 2009 New Revision: 30328 URL: http://wso2.org/svn/browse/wso2?view=rev&revision=30328
Log: Modified extensions guide page to suite carbon based ESB Modified: trunk/esb/java/docs/xdoc/extensions_guide.xml Modified: trunk/esb/java/docs/xdoc/extensions_guide.xml URL: http://wso2.org/svn/browse/wso2/trunk/esb/java/docs/xdoc/extensions_guide.xml?rev=30328&r1=30327&r2=30328&view=diff ============================================================================== --- trunk/esb/java/docs/xdoc/extensions_guide.xml (original) +++ trunk/esb/java/docs/xdoc/extensions_guide.xml Tue Feb 3 01:51:20 2009 @@ -106,7 +106,7 @@ 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 - mediation rules, local registry entries and other and configuration, while + mediation rules, local registry entries and other configuration, while the environment gives access to the underlying SOAP implementation used - Apache Axis2. A typical mediator would need to manipulate the MessageContext by referring to the SynapseConfiguration. However, it is @@ -198,7 +198,7 @@ }</pre> <p> The MessageContext interface is based on the Axis2 <a>MessageContext</a> - interface, and uses the Axis2 <a>EndpointReference</a> and + interface, and it uses the Axis2 <a>EndpointReference</a> 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 @@ -270,7 +270,7 @@ <p> 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 + mediators). A Node mediator must implement the org.apache.synapse.api.ListMediator interface listed below, or extend from the org.apache.synapse.mediators.AbstractListMediator. </p> @@ -372,21 +372,20 @@ to create and configure the custom mediator instance. A MediatorSerializer implementation defines how a configuration should be serialized back into an XML configuration. The custom MediatorFactory & MediatorSerializer - implementations and the mediator class/es must be bundled in a JAR file - conforming to the J2SE Service Provider model (See the description for - Extensions below for more details and examples) and placed into the - ESB_HOME/lib folder, so that the Synapse runtime could find and load the - definition. + implementations and the mediator class/es must be bundled as an OSGi bundle + exporting these classes (See the description for Extensions below for more + details and examples) and placed into the ESB_HOME/webapps/ROOT/WEB-INF/plugins + folder, so that the Synapse runtime could find and load the definition. </p> <p> - Essentially this means that a custom JAR file must bundle your class - implementing the Mediator interface, and the MediatorFactory - implementation class and contain two text files named + Essentially this means that a custom JAR file must bundle your classes + implementing the Mediator interface, MediatorSerializer and the MediatorFactory + interfaces. It should also contain two text files named "org.apache.synapse.config.xml.MediatorFactory" and "org.apache.synapse.config.xml.MediatorSerializer" which will contain the fully qualified name(s) of your MediatorFactory and MediatorSerializer - implementation classes. You should also place any dependency JARs into the - same lib folder so that the correct classpath references could be made. + implementation classes. Any dependencies should be made availble through OSGi + bundles in the same plugins directory. </p> <p> The MediatorFactory interface listing is given below, which you should @@ -472,9 +471,9 @@ href="http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html#Service%20Provider";>J2SE Service Provider model</a>. This essentially iterates over the available JAR files, for a META-INF/services directory within each file, - and looks for a text file with the name - org.apache.synapse.config.xml.MediatorFactory which contains a list of - fully qualified classname that implement the above interface, listing each + and looks for text files with the name + org.apache.synapse.config.xml.MediatorFactory and org.apache.synapse.config.xml.MediatorSerializer + which contains a list of fully qualified classname that implement the above interface, listing each class in a separate line. For example, the built-in synapse-extensions.jar contains the following structure: </p> _______________________________________________ Esb-java-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
