Download JAR files tagged by carbon with all dependencies

This module generates the product distribution (zip) by installing sample in-memory user store and carbon-security feature on top of kernel core and runtime features and finally assembles product specific configurations files and startup scripts using assembly plugin.

This module generates the product distribution (zip) by installing sample in-memory user store and carbon-security feature on top of kernel core and runtime features and finally assembles product specific configurations files and startup scripts using assembly plugin.

This module is common library module used by both WSO2 EI and WSO2 MI. This contains utility library modules. Note: Please follow below guides when adding new packages 1. AVOID adding any OSGI Declarative services 2. AVOID adding WSO2 specific modules as dependencies. For example: Carbon-Kernel, Carbon-Registry 3. No restrictions to add any third party dependencies (that comply with WSO2 license policies) For example: Axis2, Synapse, Axiom, etc.

There are two ways to use OSGi in server-side[1]. In Carbon, what we have done is, embedding an OSGi framework inside a servlet container. So BridgeServlet delegates all the request from the servlet container to the HttpServiceServlet registered by the http.bridge bundle. This is required only when Carbon is running inside a webapp. There is a possibility to embed an HTTP server(ex. jetty) inside equinox and start a server with all our carbon bundles. This is same as running carbon inside spring DM server. For this scenario, we do not need org.wso2.carbon.http.bridge bundles and the org.wso2.carbon.bridge extension bundle. 1. http://eclipse.org/equinox/server/http_quickstart.php