In order to make it easier for clients to add HPI to an existing Alfresco repo, it would be preferable to create a behavior that would automatically add the tsg:renditioned aspect to any types that are configured in the bean. The behavior would add the rendition to new objects and check existing objects to add the aspect if not already present. This way, client-specific types could simply be configured in the bean, and we wouldn't have to run a script to add the aspect to all existing content that requires it.
Testing/performance concerns:
We don't want a behavior firing on every single property update on cm:content type if possible... super inefficient. The challenge is how to create a configurable behavior that only acts on the injected types in the bean? May be a good discussion to have with @mbowen000 @parzgnat @dgrumieaux.
In order to make it easier for clients to add HPI to an existing Alfresco repo, it would be preferable to create a behavior that would automatically add the tsg:renditioned aspect to any types that are configured in the bean. The behavior would add the rendition to new objects and check existing objects to add the aspect if not already present. This way, client-specific types could simply be configured in the bean, and we wouldn't have to run a script to add the aspect to all existing content that requires it.
Testing/performance concerns: We don't want a behavior firing on every single property update on cm:content type if possible... super inefficient. The challenge is how to create a configurable behavior that only acts on the injected types in the bean? May be a good discussion to have with @mbowen000 @parzgnat @dgrumieaux.