Sam Mercs wrote:Seems like a pretty rare off use case to me ....
Thanks for replying.
I actually suspect many people run into this problem....
The "greeting text" example was just for simplicity. In reality, our resources are vendor-specific configuration files, required for various 3rd-party tools.
E.g. you may have some 3rd party called "AnnoyingCacheManager", and in order to configure itself it expects an InputStream to a vendor-specific xml file, such as:
Naturally I'd <thePort> to be configurable through Spring.
Now if I'm lucky, AnnoyingCacheManager might be "Spring ready" (have explicit Spring support, or some useful setters).
But some of our esoteric vendors just expect this rigid XML format
So I'd like Spring to prepare the required stream based on some template.