Provide a command line wrapper for Spring contexts
Description
Environment
Activity
Scott Cantor July 1, 2020 at 4:25 PM
A proof of concept with the DataSealer is working, but I'm going to move that up out of spring-extensions.
I'm sure there's room for improvement but it seems to be working ok.
Scott Cantor June 30, 2020 at 7:30 PM
it's early but I think it would. My motivation is the DataSealer atm.
I'm merging some of what Ian did for the MDA with what I did for the IdP and just trying to genericize it a bit, but I'm trying to avoid a situation where the actual thing you want to do has to be wired into a bean, I want to support just simple subclasses doing "work" driven by the command line args but by leveraging named beans in the Spring context you load.
Rod Widdowson June 30, 2020 at 7:25 PM
This might speak to a need I’m worrying about for the plugin installer. It needs to download from a specified URL and that opens up all the different ways to fire up an HttpClient.
I’d decided to just say ‘if it isn’t a vanilla download then you have to do it yourself’ but an easy way to invoke spring configuration would be a win.... always assuming that this is the idea here....
Evaluate possible utility classes for instantiating a context via CLI. This may go nowhere, but I'm hoping for something less than Spring Boot but with a little boilerplate.