Could you come up with a use case where manual configuration ordering
would add some value? I didn't get it. If the user configuration is
strongly typed, with well defined property names, ordering doesn't
make sense. If the user configuration is just a bunch of values, we
should use the same order the elements were specified in the
descriptor. Principle of least surprise, I think.
-- Marcus Brito
Configuration will probably come in two flavors: a strongly
On Sat, 24 Jul 2004 17:36:07 -0400, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> 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]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
