If you would start doing specific gets/sets then you might want to do
the whole configuration like that otherwise it will become a hard mix of
generic gets and specific gets. And since it is an interface adding new
specific gets/sets will break the compatibility very easy.
Sticking with loose get/sets it would be probably better. I'm using
Jakarta Configuration and injecting a Jakarta Configuration
"sub-configuration" wrapped on a Velocity configuration will work well
for me :)
On 11/29/2010 02:34 PM, Nathan Bubna wrote:
On Mon, Nov 29, 2010 at 11:24 AM, Antonio Petrelli
<[email protected]> wrote:
2010/11/29 Adrian Tarau<[email protected]>:
What I wanted to say is to follow the model and not to include any
dependency.
Ok
A minimal functionality should be to set/get primitive types and
work with lists and store everything behind as strings(with "," as separator
for lists).
Not entirely true, only "gets" are needed, since configuration is read-only.
at least it is at the present...
I do not thing there is a need for anything else then storing
bools(is feature A enabled/disabled), ints, strings and list of strings for
Velocity.
Sure, but having developer-friendly methods, like "getUserDirectives"
and such, easies the development.
Anyway let me work on it, if you don't like it we can still revert it ;-)
Antonio
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
