Change the "name=" value for the UID attribute definition for specific entityIDs

Cantor, Scott cantor.2 at
Wed Oct 4 14:14:35 EDT 2017

On 10/4/17, 1:54 PM, "users on behalf of Joseph Fischetti" <users-bounces at on behalf of Joseph.Fischetti at> wrote:

> The documentation shows a number of examples for implementing this, but doesn't mention where the bean itself should be
> defined. Am I right in saying it should go in conf/mvc-beans.xml?

That would be a very unusual and ill-advised place. Adding a resource to services.xml for that service and putting custom beans into it is the normal way. Beans should be scoped to the subsystems where they're used.

> Considering this adds complexity on the management side, are there particular reasons for/against releasing multiple versions of
> the same attribute?

It's about the same complexity either way but more confusing when I don't have anything telling me why I have a second encoder sitting there running globally and then have to leave it there forever because I'm afraid I'll break something. An activation condition is self-documenting. SP goes away and I know exactly what I did and what to remove.

-- Scott

More information about the users mailing list