So, if we do it this way, which looks great to me . . . then how do I configure the DI to inject the current Action. The TextProviderSupport needs contextual stuff from the current action, clazz and localeProvider. Also, my CustomTextProviderSupport use case requires the action, as another type of provider similar to localeProvider ( a "component" provider that provides access to the component from our system related to the current request ). So, wiring these current action bits into the textSupport still eludes me.
With this proposed fix, I would hope to enable all of this wiring as injections into my CustomTextSupport configured in my DI meta data. But I don't know how it works to reference the "current action" from this pre-runtime situation. Perhaps this is the wrong approach . . . perhaps I should be writing my CustomTextSupport so that it know's how to find it's resources in the ActionContext or ValueStack, similar to how you obtain the ObjectFactory with the getInstance method above. Can I do something like this to obtain the current Action?