Ability to inject reloadable beans to make system more dynamic
Basics
Technical
Logistics
Basics
Technical
Logistics
Description
One way of externalizing configuration would be to support flat files containing lists of entities that could be sucked in as a source for a condition to apply to some of the logic that operates on an EntityDescriptor, specifically thinking of the EntityAttributes filter.
Scripts already work, but it's a hell of a lot more efficient to load a small flat file into a set in RAM and less work for deployers than creating scriptlets given Nashorn and so forth.
Environment
None
Activity
Scott Cantor
March 28, 2018 at 12:41 AM
This was "successful" in the sense that it does work, but I wouldn't recommend it for anybody that's not incredibly comfortable with Spring and the internals of their system, and I doubt I'll get around to documenting it unless I kick the tires on it more.
Implementation and simple testing of a custom Scope, some wrapper classes, and an example that demonstrate a bean file turning part of itself into reloadable beans.
Scott Cantor
February 21, 2017 at 10:02 PM
Have been going down a rabbit hole with this to determine how generic this kind of thing could be to support a wider set of cases.
Have investigated a few Spring techniques in this area, and one of the weirder ones that probably is a really bad idea is a custom Scope implementation that would wrap a reloadable Spring context.
One way of externalizing configuration would be to support flat files containing lists of entities that could be sucked in as a source for a condition to apply to some of the logic that operates on an EntityDescriptor, specifically thinking of the EntityAttributes filter.
Scripts already work, but it's a hell of a lot more efficient to load a small flat file into a set in RAM and less work for deployers than creating scriptlets given Nashorn and so forth.