Just thought of a cool idea ... why not add some attributes to the
schema element to control the ordering of elements in a configuration?
That's the most common thing .a service does with a configuration;
instantiate an Orderer and reorder the inputs into something useful
(the second most being to convert a List into a Map).
schema (ordered="true|false" name-property="name"
following-names-property="before" preceding-names-property="after")
You would only specify name-property, following-names-property and
preceding-names-propertyif they different than the defaults ("name",
"before", "after").
The ordered attribute would default to false.
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
