net.shibboleth.utilities.java.support.component.*

[Tom Zeller]

>>>> Nameable is fine by me, and frankly Nameable and Named seem clearer and
>>>> shorter.
>>>
>>> FWIW, +1 on both of the above paragraphs from me. I think I like
>>>Nameable/Named a little better except for the suspicion that this
>>>convention might imply getName, which I don't like much.
>>
>>I was typing Nameable/Named should then provide getName() and
>>setName() ... why do you not like those ?
>
> Basically I think because in Spring, we know it's actually the bean ID.

Okay, so the BeanPostProcessor would call :

 ((NameableComponent) bean).setId(beanName);

Just FYI, the wiki says :

"IdentifiedComponent - A component that is identified by a unique
ID/name. The scope within which this ID is unique is usually, but not
always, limited to object which contains the component."

https://wiki.shibboleth.net/confluence/display/IDP30/2.+Project-wide+Patterns+and+APIs