-
Notifications
You must be signed in to change notification settings - Fork 1
/
pom.xml
93 lines (85 loc) · 3.9 KB
/
pom.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
<?xml version="1.0" encoding="utf-8"?>
<!--
~ Copyright (c) WSO2 Inc. (http://wso2.com) All Rights Reserved.
~
~ Licensed under the Apache License, Version 2.0 (the "License");
~ you may not use this file except in compliance with the License.
~ You may obtain a copy of the License at
~
~ http://www.apache.org/licenses/LICENSE-2.0
~
~ Unless required by applicable law or agreed to in writing, software
~ distributed under the License is distributed on an "AS IS" BASIS,
~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
~ See the License for the specific language governing permissions and
~ limitations under the License.
-->
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<parent>
<groupId>org.wso2.carbon</groupId>
<artifactId>carbon-kernel</artifactId>
<version>4.1.0-SNAPSHOT</version>
<relativePath>../pom.xml</relativePath>
</parent>
<modelVersion>4.0.0</modelVersion>
<artifactId>org.wso2.carbon.http.bridge</artifactId>
<packaging>bundle</packaging>
<name>WSO2 Carbon - HTTP Bridge</name>
<description>
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
</description>
<url>http://wso2.org</url>
<dependencies>
<dependency>
<groupId>org.eclipse.osgi</groupId>
<artifactId>org.eclipse.osgi</artifactId>
</dependency>
<dependency>
<groupId>org.wso2.carbon</groupId>
<artifactId>org.wso2.carbon.bridge</artifactId>
<version>${pom.version}</version>
</dependency>
<dependency>
<groupId>org.eclipse.equinox</groupId>
<artifactId>org.eclipse.equinox.http.servlet</artifactId>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<version>1.4.0</version>
<extensions>true</extensions>
<configuration>
<instructions>
<Bundle-SymbolicName>${pom.artifactId}</Bundle-SymbolicName>
<Bundle-Name>${pom.artifactId}</Bundle-Name>
<Bundle-Activator>org.wso2.carbon.http.bridge.HttpBridgeActivator</Bundle-Activator>
<Export-Package>org.wso2.carbon.http.bridge</Export-Package>
<Import-Package>
!org.wso2.carbon.http.bridge,
org.osgi.framework.*,
org.wso2.carbon.bridge.*,
org.eclipse.equinox.http.servlet,
javax.servlet; version="${imp.pkg.version.javax.servlet}",
javax.servlet.http; version="${imp.pkg.version.javax.servlet}",
*;resolution:=optional
</Import-Package>
</instructions>
</configuration>
</plugin>
</plugins>
</build>
</project>