I actually would rather see some of the Action approaches @Deprecated. Right now, there are too many ways to create an action, which leads to too many test paths for the platform, and in the future, too many upgrade paths to maintain. Also, the lack of consistency here confuses customers when trying to decide on a "best approach".
For example, just in the quickstarts alone, I have see the following ways to create actions:
Some Actions extend AbstractActionLifecycle, some implement BeanConfiguredAction, others ActionPipelineProcessor, and still others AbstractActionPipelineProcessor.