Feature #4087
take component-specific code which is coded inline in the StandardServer initialization today and move it back into those components
0%
History
#1 Updated by Greg Shah almost 5 years ago
In StandardServer.bootstrap()
and StandardServer.registerDefaultServices()
we have a great deal of code that is not really related to the StandardServer
, but is there for init/term of some unrelated FWD component.
The idea here is that this code should "live" in that component, even if we have a hard coded hook to initialize it in the standard server. This is probably pretty easy in any component that uses the AbstractInitTermListener
(i.e. the StandardServer.registerDefaultServices()
case) as we could (at a minimum) create a dedicated subclass for the component and limit the dependency in StandardServer
to a reference of that subclass.
Better still would be a registration approach, however we do have a bit of a chicken and egg problem there.
The code in StandardServer.bootstrap()
will require a different approach but surely we can do better than having all the code inline.