o

org.wso2.carbon.http.bridge

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
http://wso2.org
文件下载
文件名 操作
org.wso2.carbon.http.bridge-4.10.15.jar 下载
org.wso2.carbon.http.bridge-4.10.15.pom 下载
org.wso2.carbon.http.bridge-4.10.15-sources.jar 下载
Apache Maven
<dependency>
  <groupId>org.wso2.carbon</groupId>
  <artifactId>org.wso2.carbon.http.bridge</artifactId>
  <version>4.10.15</version>
  <type>bundle</type>
</dependency>
Gradle Groovy
implementation 'org.wso2.carbon:org.wso2.carbon.http.bridge:4.10.15'
Gradle Kotlin
implementation("org.wso2.carbon:org.wso2.carbon.http.bridge:4.10.15")
Scala SBT
libraryDependencies += "org.wso2.carbon" % "org.wso2.carbon.http.bridge" % "4.10.15"
Groovy Grape
@Grapes(
  @Grab(group='org.wso2.carbon', module='org.wso2.carbon.http.bridge', version='4.10.15')
)
Apache Ivy
<dependency org="org.wso2.carbon" name="org.wso2.carbon.http.bridge" rev="4.10.15" />
Leiningen
[org.wso2.carbon/org.wso2.carbon.http.bridge "4.10.15"]
Apache Buildr
'org.wso2.carbon:org.wso2.carbon.http.bridge:jar:4.10.15'