My vote is in line....
On 3/1/07, Asankha C. Perera <[EMAIL PROTECTED]> 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)
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>
+ 1
2. Overall configuration - decide on the name of the main element, and
noun vs verb usage
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>
+1
3. Element / Attribute naming
Option 1: <fooBar fooBar="xx"/>
+1
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:
entry
thanks
indika
