Users need to apply different external JAR files According to the existing Carbon server in order to introduce new features or to enhance the Carbon application. OSGi bundles are used to implement WSO2 Carbon. As a result, if you need to extend a platform, the OSGi bundles need to be dropped into the Carbon server.
To add external libraries:
The users are allowed to apply JARs to various directories as required. The WSO2 Carbon OSGi repository is available in the <CARBON_HOME>/repository/components directory. When extracting a Carbon or Carbon-based product, <CARBON_HOME> is the folder that gets generated.
Use the following directories to drop external libraries to the Carbon Server:
...
Carbon architecture, all functionality and features available in Carbon products are built using OSGI bundles. Therefore, it is possible to extend the features available in the Carbon platform by adding new OSGI bundles to the product build. You can also add JAR files that are not OSGI bundles into the product build, which will be converted into OSGI bundles during server startup. All these OSGI bundles/JARs are stored in the OSGI repository of the product.
The WSO2 Carbon OSGI repository
The OSGI repository is located in the <PRODUCT_HOME>/repository/components directory. The users are allowed to apply JARs/OSGI bundles to any of the following directories:
| Directory | Description | |
|---|---|---|
<PRODUCT_HOME>/repository/components/dropins | OSGi bundles that need to be applied. | <CARBONThird-party libraries, which are already OSGI bundles. |
<PRODUCT_HOME>/repository/components/lib | JAR files that will be converted to OSGi bundles at startup and copied to the dropins directory during server startup. | |
<CARBON<PRODUCT_HOME>/repository/components/extensions | JAR files that will be converted to OSGi Framework Extension bundles at startup and copied to the dropins directory during server startup. |
| Info |
|---|
| Note |
Note that it is not recommend to manually edit the |
...
. |