Actions should not be Identifiable ?

Cantor, Scott cantor.2 at osu.edu
Mon Mar 24 22:39:28 EDT 2014


On 3/24/14, 10:31 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:
>
>Well, I guess what is bothering me is that our design[1] says that
>Components have a "unique identifier", which is not actually the case,
>and that unique ID is used mostly for logging and Spring - but is
>defined in a module (java-support) which is specifically Spring
>independent.

I don't think we need it *for* Spring, but we're trying to avoid
duplication by overloading the Spring ID into the "component" ID for the
cases where we need one.

I think the few cases where it's useful for logging are in fact quite
isolated:

- metadata providers
- resolver definitions
- filter policies and rules

A few others...?

I don't think they're the majority.

-- Scott




More information about the dev mailing list