In version 7.0, Digital Factory introduced the possibility to use OSGi to package and distribute Digital Factory modules. This means that you can now dynamically deploy and undeploy modules into a Digital Experience Manager installation, making it easier to manage modules during both development and production phases.
In the following table we show the main differences in module development before and after OSGi introduction in Jahia’s Digital Experience Manager.
Before OSGi | With OSGi | |
---|---|---|
Class or library deployment | Requires web app restart | No restart needed |
Module is "exploded" on deployment | ||
Quick changes to source files don't require deployment | Only works in exploded directory, not module's source | |
External libraries are deployed into WEB-INF/lib and exposed to all other modules | ||
Undeployment cleans up everything immediately | ||
Modules depending on others cannot be deployed without their dependency | ||
Modules started/stopped after installation |
For administrators:
For developers:
Copyrights © 2002-2020 All Rights Reserved by Jahia Solutions Group SA