Hi Andreas, I couldn't hot deploy my proxy configuration using the proof-of-concept you have mentioned.
May be I am missing out something simple. When you mention repository, do we need to configure the repository location somewhere? I am attaching the axis2.xml I have used and the proxy config xml file. And referring to Asankha's mail, are you planning to provide the ability to load the proxy services from the registry too. If so, when will be the expected release date ? --------------- Regards, Shradha -----Original Message----- From: Andreas Veithen [mailto:[email protected]] Sent: Tuesday, December 30, 2008 11:45 PM To: [email protected] Subject: Re: Dynamically loading proxy configuration in synapse.xml Hi Shradha, This is not yet supported by Synapse (see [1] for a similar request). I think that it is possible to satisfy this requirement by implementing an Axis2 custom deployer. I put together a working proof-of-concept (well, more or less working, see below), which will be available in the next nightly build (build #222; see [2]). In order to play with it, you need to do the following: 1) In axis2.xml, add the following line: <deployer extension="xml" directory="proxies" class="org.apache.synapse.experimental.ProxyDeployer"/> 2) Still in axis2.xml, change the "hotdeployment" parameter to true. 3) In your repository, create a directory called "proxies". 4) Start up Synapse. 5) Drop a file into the "proxies" directory with the proxy definition. The suffix must be ".xml" and the root element "proxy" (in the standard Synapse configuration namespace): <proxy xmlns="http://ws.apache.org/ns/synapse"; name="..."> ... </proxy> Synapse will then automatically deploy this new proxy. The bad news is that for the moment it only works in hot deployment mode, i.e. if the file is added after Synapse has been started. Deployment of the proxy service fails if the file is already present during startup. The reason is that the custom deployer requires access to the SynapseConfiguration object, which is created by the SynapseInitializationModule. However, this module is only initialized after Axis2 attempts the deployment. This problem is of course a show-stopper, but maybe somebody else on this list has a brilliant idea how to change the order in which things happen at startup? Regards, Andreas [1] https://issues.apache.org/jira/browse/SYNAPSE-346 [2] http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache .synapse$synapse-distribution/lastBuild/ On Tue, Dec 30, 2008 at 12:29, <[email protected]> wrote: > Hi All, > > I have a requirement in which after starting synapse, I need to add > proxy configurations to synapse.xml. > > But I guess synapse does not dynamically reload the proxy > configurations and I need to restart my synapse ( which may result in > existing proxy services getting stopped ) > > I want my ESB to act as a proxy for different endpoints routing the > messages through the same insequence. > > And I want to dynamically add these proxy configurations when I need. > > What are the possible ways to achieve my objective? > > --------------- > > Thanks, > > Shradha > > > > Please do not print this email unless it is absolutely necessary. > > The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. > > WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. > > www.wipro.com > Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
<!-- ~ Licensed to the Apache Software Foundation (ASF) under one ~ or more contributor license agreements. See the NOTICE file ~ distributed with this work for additional information ~ regarding copyright ownership. The ASF licenses this file ~ to you under the Apache License, Version 2.0 (the ~ "License"); you may not use this file except in compliance ~ with the License. You may obtain a copy of the License at ~ ~ http://www.apache.org/licenses/LICENSE-2.0 ~ ~ Unless required by applicable law or agreed to in writing, ~ software distributed under the License is distributed on an ~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY ~ KIND, either express or implied. See the License for the ~ specific language governing permissions and limitations ~ under the License. --> <axisconfig name="AxisJava2.0"> <!-- ================================================= --> <!-- Parameters --> <!-- ================================================= --> <parameter name="hotdeployment">true</parameter> <parameter name="hotupdate">false</parameter> <parameter name="enableMTOM">false</parameter> <parameter name="enableSwA">false</parameter> <!--Uncomment if you want to enable file caching for attachments --> <!--parameter name="cacheAttachments">true</parameter> <parameter name="attachmentDIR"></parameter> <parameter name="sizeThreshold">4000</parameter--> <!--This will give out the timout of the configuration contexts, in milliseconds--> <parameter name="ConfigContextTimeoutInterval">30000</parameter> <!--During a fault, stacktrace can be sent with the fault message. The following flag will control --> <!--that behavior.--> <parameter name="sendStacktraceDetailsWithFaults">false</parameter> <!--If there aren't any information available to find out the fault reason, we set the message of the exception--> <!--as the faultreason/Reason. But when a fault is thrown from a service or some where, it will be --> <!--wrapped by different levels. Due to this the initial exception message can be lost. If this flag--> <!--is set, then Axis2 tries to get the first exception and set its message as the faultreason/Reason.--> <parameter name="DrillDownToRootCauseForFaultReason">false</parameter> <parameter name="userName">admin</parameter> <parameter name="password">axis2</parameter> <!--To override repository/services you need to uncomment following parameter and value SHOULD be absolute file path.--> <!--ServicesDirectory only works on the following cases--> <!---File based configurator and in that case the value should be a file URL (http:// not allowed)--> <!---When creating URL Based configurator with URL "file://" --> <!--- War based configurator with expanded case , --> <!--All the other scenarios it will be ignored.--> <!--<parameter name="ServicesDirectory">service</parameter>--> <!--To override repository/modules you need to uncomment following parameter and value SHOULD be absolute file path--> <!--<parameter name="ModulesDirectory">modules</parameter>--> <!--Following params will set the proper context paths for invocations. All the endpoints will have a commons context--> <!--root which can configured using the following contextRoot parameter--> <parameter name="contextRoot">/</parameter> <!--Our HTTP endpoints can handle both REST and SOAP. Following parameters can be used to distinguiush those endpoints--> <!--In case of a servlet, if you change this you have to manually change the settings of your servlet container to map this --> <!--context path to proper Axis2 servlets--> <parameter name="servicePath">services</parameter> <parameter name="restPath">rest</parameter> <!-- Following parameter will completely disable REST handling in Axis2--> <parameter name="disableREST" locked="true">false</parameter> <!-- Extension deployer ***** Uncomment the following line to enable (hot) deployment of Synapse extensions (mediators and startups) ***** --> <!--<deployer extension="xar" directory="extensions" class="org.apache.synapse.core.axis2.ExtensionDeployer"/>--> <deployer extension="xml" directory="proxies" class="org.apache.synapse.experimental.ProxyDeployer"/> <!-- Following parameter will set the host name for the epr--> <!--<parameter name="hostname" locked="true">myhost.com</parameter>--> <!-- If you have a frontend host which exposes this webservice using a different public URL --> <!-- use this parameter to override autodetected url --> <!--<parameter name="httpFrontendHostUrl">https://someotherhost/context</parameter>--> <!-- The way of adding listener to the system--> <!-- <listener class="org.apache.axis2.ObserverIMPL">--> <!-- <parameter name="RSS_URL">http://127.0.0.1/rss</parameter>--> <!-- </listener>--> <!-- ================================================= --> <!-- Message Receivers --> <!-- ================================================= --> <!--This is the deafult MessageReceiver for the system , if you want to have MessageReceivers for --> <!--all the other MEP implement it and add the correct entry to here , so that you can refer from--> <!--any operation --> <!--Note : You can ovrride this for a particular service by adding the same element with your requirement--> <messageReceivers> <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-only"; class="org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver"/> <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-out"; class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/> <messageReceiver mep="http://www.w3.org/2006/01/wsdl/in-only"; class="org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver"/> <messageReceiver mep="http://www.w3.org/2006/01/wsdl/in-out"; class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/> </messageReceivers> <!-- ================================================= --> <!-- Message Formatter --> <!-- ================================================= --> <!--Following content type to message formatter mapping can be used to implement support for different message --> <!--format serialization in Axis2. These message formats are expected to be resolved based on the content type. --> <messageFormatters> <messageFormatter contentType="application/x-www-form-urlencoded" class="org.apache.axis2.transport.http.XFormURLEncodedFormatter"/> <messageFormatter contentType="multipart/form-data" class="org.apache.axis2.transport.http.MultipartFormDataFormatter"/> <messageFormatter contentType="application/xml" class="org.apache.axis2.transport.http.ApplicationXMLFormatter"/> <!--<messageFormatter contentType="x-application/hessian" class="org.apache.synapse.format.hessian.HessianMessageFormatter"/>--> <!--<messageFormatter contentType="" class="org.apache.synapse.format.hessian.HessianMessageFormatter"/>--> </messageFormatters> <!-- ================================================= --> <!-- Message Builders --> <!-- ================================================= --> <!--Following content type to builder mapping can be used to implement support for different message --> <!--formats in Axis2. These message formats are expected to be resolved based on the content type. --> <messageBuilders> <messageBuilder contentType="application/xml" class="org.apache.axis2.builder.ApplicationXMLBuilder"/> <messageBuilder contentType="application/x-www-form-urlencoded" class="org.apache.axis2.builder.XFormURLEncodedBuilder"/> <messageBuilder contentType="multipart/form-data" class="org.apache.axis2.builder.MultipartFormDataBuilder"/> <!--<messageBuilder contentType="x-application/hessian" class="org.apache.synapse.format.hessian.HessianMessageBuilder"/>--> <!--<messageBuilder contentType="" class="org.apache.synapse.format.hessian.HessianMessageBuilder"/>--> </messageBuilders> <!-- ================================================= --> <!-- Transport Ins --> <!-- ================================================= --> <!-- the non blocking http transport based on HttpCore + NIO extensions --> <transportReceiver name="http" class="org.apache.synapse.transport.nhttp.HttpCoreNIOListener"> <parameter name="port">8280</parameter> <parameter name="non-blocking">true</parameter> <!--parameter name="bind-address" locked="false">hostname or IP address</parameter--> <!--parameter name="WSDLEPRPrefix" locked="false">https://apachehost:port/somepath</parameter--> </transportReceiver> <!-- the non blocking https transport based on HttpCore + SSL-NIO extensions --> <transportReceiver name="https" class="org.apache.synapse.transport.nhttp.HttpCoreNIOSSLListener"> <parameter name="port" locked="false">8243</parameter> <!--parameter name="bind-address" locked="false">hostname or IP address</parameter--> <!--parameter name="WSDLEPRPrefix" locked="false">http://apachehost:port/somepath</parameter--> <parameter name="non-blocking" locked="false">true</parameter> <parameter name="keystore" locked="false"> <KeyStore> <Location>lib/identity.jks</Location> <Type>JKS</Type> <Password>password</Password> <KeyPassword>password</KeyPassword> </KeyStore> </parameter> <parameter name="truststore" locked="false"> <TrustStore> <Location>lib/trust.jks</Location> <Type>JKS</Type> <Password>password</Password> </TrustStore> </parameter> <!--<parameter name="SSLVerifyClient">require</parameter> supports optional|require or defaults to none --> </transportReceiver> <!--Uncomment this and configure as appropriate for JMS transport support, after setting up your JMS environment (e.g. ActiveMQ) <transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener"> <parameter name="myTopicConnectionFactory"> <parameter name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter> <parameter name="java.naming.provider.url">tcp://localhost:61616</parameter> <parameter name="transport.jms.ConnectionFactoryJNDIName">TopicConnectionFactory</parameter> <parameter name="transport.jms.ConnectionFactoryType" locked="false">topic</parameter> </parameter> <parameter name="myQueueConnectionFactory"> <parameter name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter> <parameter name="java.naming.provider.url">tcp://localhost:61616</parameter> <parameter name="transport.jms.ConnectionFactoryJNDIName">QueueConnectionFactory</parameter> <parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter> </parameter> <parameter name="default"> <parameter name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter> <parameter name="java.naming.provider.url">tcp://localhost:61616</parameter> <parameter name="transport.jms.ConnectionFactoryJNDIName">QueueConnectionFactory</parameter> <parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter> </parameter> </transportReceiver>--> <transportReceiver name="vfs" class="org.apache.synapse.transport.vfs.VFSTransportListener"/> <transportReceiver name="mailto" class="org.apache.axis2.transport.mail.MailTransportListener"> <!-- configure any optional POP3/IMAP properties check com.sun.mail.pop3 and com.sun.mail.imap package documentation for more details--> </transportReceiver> <!--Uncomment this for FIX transport support <transportReceiver name="fix" class="org.apache.synapse.transport.fix.FIXTransportListener"> <parameter name="non-blocking">true</parameter> </transportReceiver>--> <!-- ================================================= --> <!-- Transport Outs --> <!-- ================================================= --> <transportSender name="http" class="org.apache.synapse.transport.nhttp.HttpCoreNIOSender"> <parameter name="non-blocking" locked="false">true</parameter> </transportSender> <transportSender name="https" class="org.apache.synapse.transport.nhttp.HttpCoreNIOSSLSender"> <parameter name="non-blocking" locked="false">true</parameter> <parameter name="keystore" locked="false"> <KeyStore> <Location>lib/identity.jks</Location> <Type>JKS</Type> <Password>password</Password> <KeyPassword>password</KeyPassword> </KeyStore> </parameter> <parameter name="truststore" locked="false"> <TrustStore> <Location>lib/trust.jks</Location> <Type>JKS</Type> <Password>password</Password> </TrustStore> </parameter> <!--<parameter name="HostnameVerifier">DefaultAndLocalhost</parameter> supports Strict|AllowAll|DefaultAndLocalhost or the default if none specified --> </transportSender> <transportSender name="jms" class="org.apache.axis2.transport.jms.JMSSender"> <!-- uncomment this and configure to use connection pools for sending messages <parameter name="myTopicConnectionFactory"> <parameter name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter> <parameter name="java.naming.provider.url">tcp://localhost:61616</parameter> <parameter name="transport.jms.ConnectionFactoryJNDIName">TopicConnectionFactory</parameter> </parameter> <parameter name="myQueueConnectionFactory"> <parameter name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter> <parameter name="java.naming.provider.url">tcp://localhost:61616</parameter> <parameter name="transport.jms.ConnectionFactoryJNDIName">QueueConnectionFactory</parameter> </parameter> <parameter name="default"> <parameter name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter> <parameter name="java.naming.provider.url">tcp://localhost:61616</parameter> <parameter name="transport.jms.ConnectionFactoryJNDIName">QueueConnectionFactory</parameter> </parameter> --> </transportSender> <transportSender name="vfs" class="org.apache.synapse.transport.vfs.VFSTransportSender"/> <!-- Uncomment and configure the SMTP server information check com.sun.mail.smtp package documentation for descriptions of properties <transportSender name="mailto" class="org.apache.synapse.transport.mail.MailTransportSender"> <parameter name="mail.smtp.host">smtp.gmail.com</parameter> <parameter name="mail.smtp.port">587</parameter> <parameter name="mail.smtp.starttls.enable">true</parameter> <parameter name="mail.smtp.auth">true</parameter> <parameter name="mail.smtp.user">synapse.demo.0</parameter> <parameter name="mail.smtp.password">mailpassword</parameter> <parameter name="mail.smtp.from">[email protected]</parameter> </transportSender>--> <!--Uncomment this for FIX transport support <transportSender name="fix" class="org.apache.synapse.transport.fix.FIXTransportSender"> <parameter name="non-blocking">true</parameter> </transportSender>--> <!-- ================================================= --> <!-- Global Modules --> <!-- ================================================= --> <!-- Comment this to disable Addressing --> <module ref="addressing"/> <module ref="synapse"/> <!--Configuring module , providing parameters for modules whether they refer or not--> <!--<moduleConfig name="addressing">--> <!--<parameter name="addressingPara">N/A</parameter>--> <!--</moduleConfig>--> <!-- ================================================= --> <!-- Clustering --> <!-- ================================================= --> <!-- Configure the following for preparing Synapse to a clustered environment --> <cluster class="org.apache.axis2.clustering.tribes.TribesClusterManager" enable="false"> <!-- This parameter indicates whther the cluster has to be automatically initalized when the AxisConfiguration is built. If set to "true" the initialization will not be done at that stage, and some other party will have to explictly initialize the cluster. --> <parameter name="AvoidInitiation">false</parameter> <!-- The membership scheme used in this setup. The only values supported at the moment are "multicast" and "wka" 1. multicast - membership is automatically discovered using multicasting 2. wka - Well-Known Address based multicasting. Membership is discovered with the help of one or more nodes running at a Well-Known Address. New members joining a cluster will first connect to a well-known node, register with the well-known node and get the membership list from it. When new members join, one of the well-known nodes will notify the others in the group. When a member leaves the cluster or is deemed to have left the cluster, it will be detected by the Group Membership Service (GMS) using a TCP ping mechanism. --> <parameter name="membershipScheme">multicast</parameter> <!-- The clustering domain/group. Nodes in the same group will belong to the same multicast domain. There will not be interference between nodes in different groups. --> <parameter name="domain">apache.synapse.domain</parameter> <!-- When a Web service request is received, and processed, before the response is sent to the client, should we update the states of all members in the cluster? If the value of this parameter is set to "true", the response to the client will be sent only after all the members have been updated. Obviously, this can be time consuming. In some cases, such this overhead may not be acceptable, in which case the value of this parameter should be set to "false" --> <parameter name="synchronizeAll">true</parameter> <!-- The maximum number of times we need to retry to send a message to a particular node before giving up and considering that node to be faulty --> <parameter name="maxRetries">10</parameter> <!-- The multicast address to be used --> <parameter name="mcastAddress">228.0.0.4</parameter> <!-- The multicast port to be used --> <parameter name="mcastPort">45564</parameter> <!-- The frequency of sending membership multicast messages (in ms) --> <parameter name="mcastFrequency">500</parameter> <!-- The time interval within which if a member does not respond, the member will be deemed to have left the group (in ms) --> <parameter name="memberDropTime">3000</parameter> <!-- The IP address of the network interface to which the multicasting has to be bound to. Multicasting would be done using this interface. --> <parameter name="mcastBindAddress">127.0.0.1</parameter> <!-- The host name or IP address of this member --> <parameter name="localMemberHost">127.0.0.1</parameter> <!-- The TCP port used by this member. This is the port through which other nodes will contact this member --> <parameter name="localMemberPort">4000</parameter> <!-- The list of static or well-known members. These entries will only be valid if the "membershipScheme" above is set to "wka" --> <members> <member> <hostName>127.0.0.1</hostName> <port>4000</port> </member> <member> <hostName>127.0.0.1</hostName> <port>4001</port> </member> </members> <!-- Enable the load balancer entry if you need to run this node as a load balancer. Multiple application domains with different LoadBalanceEventHandler implementations can be defined in this section. --> <loadBalancer enable="false"> <applicationDomain name="apache.axis2.app.domain" handler="org.apache.axis2.clustering.DefaultLoadBalanceEventHandler"/> </loadBalancer> <!-- This interface is responsible for handling context replication. The property changes in the Axis2 context hierarchy in this node, are propagated to all other nodes in the cluster. The "excludes" patterns can be used to specify the prefixes (e.g. local_*) or suffixes (e.g. *_local) of the properties to be excluded from replication. The pattern "*" indicates that all properties in a particular context should not be replicated. The "enable" attribute indicates whether context replication has been enabled --> <contextManager class="org.apache.axis2.clustering.context.DefaultContextManager" enable="false"> <listener class="org.apache.axis2.clustering.context.DefaultContextManagerListener"/> <replication> <defaults> <exclude name="local_*"/> <exclude name="LOCAL_*"/> </defaults> <context class="org.apache.axis2.context.ConfigurationContext"> <exclude name="UseAsyncOperations"/> <exclude name="SequencePropertyBeanMap"/> </context> <context class="org.apache.axis2.context.ServiceGroupContext"> <exclude name="my.sandesha.*"/> </context> <context class="org.apache.axis2.context.ServiceContext"> <exclude name="my.sandesha.*"/> </context> </replication> </contextManager> </cluster> <!-- ================================================= --> <!-- Phases --> <!-- ================================================= --> <phaseOrder type="InFlow"> <!-- System pre defined phases --> <phase name="Transport"> <handler name="RequestURIBasedDispatcher" class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"> <order phase="Transport"/> </handler> <handler name="SOAPActionBasedDispatcher" class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"> <order phase="Transport"/> </handler> </phase> <phase name="Addressing"> <handler name="AddressingBasedDispatcher" class="org.apache.axis2.dispatchers.AddressingBasedDispatcher"> <order phase="Addressing"/> </handler> </phase> <phase name="Security"/> <phase name="PreDispatch"/> <phase name="Dispatch" class="org.apache.axis2.engine.DispatchPhase"> <handler name="CustomURIBasedDispatcher" class="org.apache.synapse.core.axis2.CustomURIBasedDispatcher"/> <handler name="RequestURIBasedDispatcher" class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/> <handler name="SOAPActionBasedDispatcher" class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/> <handler name="RequestURIOperationDispatcher" class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/> <handler name="SOAPMessageBodyBasedDispatcher" class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/> <handler name="HTTPLocationBasedDispatcher" class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/> </phase> <phase name="RMPhase"/> <!-- System predefined phases --> <!-- After Postdispatch phase module author or service author can add any phase he want --> <phase name="OperationInPhase"/> <phase name="soapmonitorPhase"/> </phaseOrder> <phaseOrder type="OutFlow"> <!-- user can add his own phases to this area --> <phase name="soapmonitorPhase"/> <phase name="OperationOutPhase"/> <!--system predefined phase--> <!--these phase will run irrespective of the service--> <phase name="RMPhase"/> <phase name="PolicyDetermination"/> <phase name="MessageOut"/> <phase name="Security"/> </phaseOrder> <phaseOrder type="InFaultFlow"> <phase name="Addressing"> <handler name="AddressingBasedDispatcher" class="org.apache.axis2.dispatchers.AddressingBasedDispatcher"> <order phase="Addressing"/> </handler> </phase> <phase name="Security"/> <phase name="PreDispatch"/> <phase name="Dispatch" class="org.apache.axis2.engine.DispatchPhase"> <handler name="RequestURIBasedDispatcher" class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/> <handler name="SOAPActionBasedDispatcher" class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/> <handler name="RequestURIOperationDispatcher" class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/> <handler name="SOAPMessageBodyBasedDispatcher" class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/> <handler name="HTTPLocationBasedDispatcher" class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/> </phase> <phase name="RMPhase"/> <!-- user can add his own phases to this area --> <phase name="OperationInFaultPhase"/> <phase name="soapmonitorPhase"/> </phaseOrder> <phaseOrder type="OutFaultFlow"> <!-- user can add his own phases to this area --> <phase name="soapmonitorPhase"/> <phase name="OperationOutFaultPhase"/> <phase name="RMPhase"/> <phase name="PolicyDetermination"/> <phase name="MessageOut"/> <phase name="Security"/> </phaseOrder> </axisconfig>
<xmlns:proxy xmlns="http://ws.apache.org/ns/synapse"; name="SimpleISV1Proxy" > <xmlns:target> <xmlns:endpoint> <xmlns:address uri="http://localhost:8080/ISV1/services/ISV1"/> </xmlns:endpoint> <xmlns:inSequence> <xmlns:log level="full" separator=","/> </xmlns:inSequence> </xmlns:target> </xmlns:proxy>
