Jahia uses OSGi to package and distribute Jahia modules. This means that you can now dynamically deploy and undeploy modules into a Jahia installation, making it easier to manage modules during both development and production phases.
This table show the main differences in traditional extensions development in non-OSGi (competing) systems and Jahia OSGi platform.
Non OSGi platforms | Jahia (with OSGi) | |
---|---|---|
Class or library deployment | Requires web app restart | No restart needed |
Module is "exploded" on deployment | Yes | No |
Quick changes to source files don't require deployment | Only works in exploded directory, not module's source | Yes |
External libraries are deployed into WEB-INF/lib and exposed to all other modules | Yes | No |
Undeployment cleans up everything immediately | No | Yes |
Modules depending on others cannot be deployed without their dependency | No | Yes |
Modules started/stopped after installation | No | Yes |
For administrators
pplication/modules
directory at deploymentFor developers
Did you find what you're looking for?
Copyrights © 2002-2022 All Rights Reserved by Jahia Solutions Group SA
Privacy Policy / Terms of Use / Legal / Login