Hi, J and Ashish.
A colleague of mine was trying to use @Inject to inject a runtime
String value (the name of the host where the application is running) into a class that had no constructor and only contains static utility methods. The value came up empty, of course. That started a discussion about how one could annotate this class (such as @Component) in order to ensure that Spring instantiated it, or if it should be added to the application context. But that begs the question, why would you want to do that?
So, the question for you guys is: are there any situations you have found where it made sense to have the Spring application context manage a bean that provided only static methods?
Thank you.