Description
Right now a TextProvider interface is implemented by the ActionSupport class which can be misleading and hard to distinguish as bean when it comes to injecting a proper implementation (e.g. using Spring).
Separating the TextProvider interface from how it is built should solve the problem.
Attachments
Issue Links
- is related to
-
WW-3905 The TextProvider injection in ActionSupport isn't quite integrated into the framework's core DI
-
- Closed
-
- links to
