Hi folks:
Chiming in a little late, but here's my votes/comments.
1. main sequence and fault sequence
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.
+1 for this option, BUT (and this is a big but) can we please not have
Synapse come out of the box configured to be a huge security hole? Open
proxies (http://en.wikipedia.org/wiki/Open_proxy) are generally bad
policy, and while it should be possible for people to configure their
Synapse installations to forward any/all messages, it absolutely should
not default to those settings. So, I vote that we make synapse by
default simply drop all messages. If you want to enable a "main"
sequence which contains <send>, by all means - we could even leave it in
the config file commented out (with an appropriate warning).
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 to this structure, but I prefer "config" (or "synapse") to
"definitions", to avoid potential confusion with WSDL.
In general I believe XML config should be nouns, since they're more
declarative where verbs imply a more procedural orientation.
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
Pick one: insert-registry, entry, registry-entry, define-entry, local-entry
Of these I like <entry> best. Since this structure in many ways mirrors
the Axis context hierarchy (a stack of contexts where you can ask for a
value and you get back the one closest to your level), I might also
suggest <property>.
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
