Said problem will get resolved if the class implementing ApplicationContextAware is marked with @Component annotation and class/residing package is mentioned as part of @ComponentScan annotation. If the class is not part of the scanned packages, then this won't work.
Do not want to initialise new Context as I need to extend the properties of the main application, is there any alternative for this.
In short, I have an utility which is built with spring framework, callee application will also be implemented using Spring, but the utility does not have control over the packages that needs to be mentioned under @ComponentScan.