So, what's the verdict? Its been 4+ days since the vote was started; let's count the results and get on with it.

Sanjiva.

Asankha C. Perera wrote:
Ok.. let us recap and try to finalize the changes we are about to make with a vote

1. main sequence and fault sequence
The main sequence executes for all messages that are handled through message mediation (i.e. not targeted to a proxy)

Option1: Write main mediation sequence within the synapse configurations' main/enclosing tag. (NOTE: the <rules> tag has been dropped, and it is possible that you define a couple of mediators followed by say an endpoint definition and then another few mediators etc. if you want! This is more like scripting languages)
<synapse xmlns="..."
   ...
   mediator*
   ........
   mediator*
   ...
</synapse>


Option 2: Expect a <sequence key="main"....> and an <sequence key="fault"...> on the local registry, or remote registry if a local definition does not exist. If neither can be found, default to a <send> and <log> respectively.

<synapse xmlns="..."
   <sequence key="main">
      mediator+
   </sequence>?
   <sequence key="fault"....>?
   ...
</synapse>


2. Overall configuration - decide on the name of the main element, and noun vs verb usage
Option1:
<synapse xmlns="http://ws.apache.org/ns/synapse";>
   <define-registry../>
   <define-proxy..../>
   <define-sequence.../>
   <define-endpoint..../>
   ...
</synapse>

Option 2: This is similar to a WSDL - but note that we are using the Synapse NS
<definitions xmlns="http://ws.apache.org/ns/synapse";>
   <registry../>
   <proxy..../>
   <sequence.../>
   <endpoint..../>
   ...
</definitions>

Option 3:
<synapse xmlns="http://ws.apache.org/ns/synapse";>
   <definitions>
       <registry../>
       <proxy..../>
       <sequence.../>
       <endpoint..../>
      ...
   </definitions>
</synapse>

3. Element / Attribute naming
Option 1: <fooBar fooBar="xx"/>
Option 2: <fooBar foo-bar="xx"/>
Option 3: <foo-bar foo-bar="xx"/>
Option 4: <foo-bar fooBar="xx"/>

4. Element name that defines a local registry entry that would override a remote registry entry with the same name
   <elementname key="string"  [src="url"]>
     string? | <inline-xml/>?
  <elementname/>

Depending on the result of question # 2 for the outer element name:

   <synapse ...>
         ...
<insert-registry | entry | define-entry | registry-entry | local-entry >
         ...
   </synapse>

   <definitions ...>
         ...
         <insert-registry  | entry | registry-entry | local-entry >
         ...
   </definitions>

Pick one: insert-registry, entry, registry-entry, define-entry, local-entry


thanks
asankha

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Director; Open Source Initiative; http://www.opensource.org/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to