Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ws Wiki" for change 
notification.

The following page has been changed by PaulFremantle:
http://wiki.apache.org/ws/SynapseUserGuide

------------------------------------------------------------------------------
  <addressing/>
  
  <!—Logs the message -->
- <log/>
+         <log/>
  </stage>
  
  <stage name="stage2-service-specific" >
@@ -84, +84 @@

  }}}
  
  
- This example demonstrates stage, regex and some built in mediators: log, 
addressing and header. It does not demonstrate the xpath, in or out rules.
+ This example demonstrates ''stage'', ''regex'' and some built in mediators: 
''log'', ''addressing'' and ''header''. It does not demonstrate the ''xpath'', 
''in'' or ''out'' rules.
  
  Every stage will be executed for each message. The first stage does initial 
processing including parsing the addressing headers and logging the message.
  
@@ -92, +92 @@

  
  Finally the last stage sends the message on. For responses, the messages come 
back through the same stages. This time the message will not be redirected 
because the “to” address on the response will not match xmethods.
  
- ==User Mediators==
+ == User Mediators ==
  
- Synapse allows users to extend the built in mediators and add their own. The 
mediators use the Synapse API. The API has three interfaces. The primary 
interface is the SynapseMessage
+ Synapse allows users to extend the built in mediators and add their own. The 
mediators use the Synapse API. The API has three interfaces. The primary 
interface is the SynapseMessage interface:
+  
+ {{{
+ public interface SynapseMessage {
+ 
+       public SOAPEnvelope getEnvelope();
+       public void setEnvelope(SOAPEnvelope envelope) throws AxisFault;
+ 
+       public EndpointReference getTo();
+       public void setTo(EndpointReference reference);
+         // lots more header get/setters not shown
+         // and a few other things ... see the real code 
+ 
+       public Object getProperty(String key);
+       public void setProperty(String key, Object value);
+ 
+       public void setResponse(boolean b);
+       public boolean isResponse();
+ }
+ 
+ }}}
+ 
+ The SynapseMessage interface is based on the Axis2 MessageContext interface. 
It uses the Axis2 EndpointReference and SOAPEnvelope classes
  
  ==In and Out==
  We could have been more explicit that the redirection is only designed to 
apply to “in” messages by using the <in> rule.

Reply via email to