[wildfly-dev] question 2 sec boot time of WISE

Alessio Soldano asoldano at redhat.com
Sun Sep 4 18:20:54 EDT 2016


Il 31/08/2016 20:51, Jason Greene ha scritto:
>> 1. lazy deployment of the utility
> What did you have in mind? This sounds tricky. You could perhaps have the subsystem register an http handler that dynamically installs the server, but if you are going that far it’s best to just register the components directly as part of the subsystem than in a deployment.
I've thought about this a bit tonight...yes, the wise.war could be 
exploded, its classes moved into the subsystem and the gtw and wise core 
jars left as external libs in their own modules. As for the lazy start, 
how about a service in the new wise subsystem that uses the WebHost 
service to start the servlet app (would need to provide it with a 
classloader including the required external libs mentioned before)? That 
could be triggered (on/off) by operations in the subsystem. Then the 
user would basically have to enable the gui using management (hal, cli).

Cheers
Alessio


-- 
Alessio Soldano
Web Service Lead, JBoss



More information about the wildfly-dev mailing list