Paul
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
To employ uniqueness checking of an actionId, I added to
addActionConfig. That method currently overwrites any actionConfigs that
are duplicate -- the last one is the winner. Should I take the same
approach for duplicate ids? Or should I throw an exception on
duplication? I'd like some guidance here because I don't know which
makes more sense; I tend towards throwing an error (duplicate ids
smell), but history allows the last one win.
