Red Hat JBoss Fuse 6.2.1 Deploying into Apache Karaf

172 Pages·2016·1.07 MB·English

Red Hat JBoss Fuse 6.2.1
Deploying into Apache Karaf
Deploying application packages into the Apache Karaf container
Last Updated: 2017-09-21

Red Hat JBoss Fuse 6.2.1 Deploying into Apache Karaf
Deploying application packages into the Apache Karaf container
JBoss A-MQ Docs Team
Content Services
[email protected]
Legal Notice
Copyright © 2015 Red Hat.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons
Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is
available at
http://creativecommons.org/licenses/by-sa/3.0/
. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must
provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert,
Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity
logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other
countries.
Linux ® is the registered trademark of Linus Torvalds in the United States and other countries.
Java ® is a registered trademark of Oracle and/or its affiliates.
XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United
States and/or other countries.
MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and
other countries.
Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally related
to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack ® Word Mark and OpenStack logo are either registered trademarks/service marks
or trademarks/service marks of the OpenStack Foundation, in the United States and other
countries and are used with the OpenStack Foundation's permission. We are not affiliated with,
endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
Abstract
The guide describes the options for deploying applications into a Red Hat JBoss Fuse container.
Table of Contents
Table of Contents
.P .A . .R . T. .I .. .T .H . E. . R. .E . D. . H. .A . T. . J. B. .O . .S .S . .F .U . .S .E . .C . O. .N . T. .A . I.N . E. .R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.C .H . A. . P. T. .E . R. . 1. .. R. .E .D . . H . .A . T. .J . B. .O . S. .S . F. .U . S. .E . .O . V. .E .R . V. .I .E . W. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1. RED HAT JBOSS FUSE CONTAINER ARCHITECTURE 5
1.2. DEPLOYMENT MODELS 6
1.3. DEPENDENCY INJECTION FRAMEWORKS 8
1.4. SYNCHRONOUS COMMUNICATION 9
1.5. ASYNCHRONOUS COMMUNICATION 10
1.6. FUSE FABRIC 11
.C .H . A. . P. T. .E . R. . 2. .. D. . E. P. .E . N. .D . E. .N . C. .Y . .I N. .J . E. .C .T . I.O . .N . .F .R . A. .M . .E . W. .O . .R . K. .S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 .3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1. SPRING AND BLUEPRINT FRAMEWORKS 13
2.2. HOT DEPLOYMENT 15
2.3. USING OSGI CONFIGURATION PROPERTIES 17
.C .H . A. . P. T. .E . R. . 3. .. B. .U . .I L. D. . I.N . G. . W. . I.T . H. . M. .A . .V .E . N. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 .9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1. MAVEN DIRECTORY STRUCTURE 19
3.2. PREPARING TO USE MAVEN 21
.C .H . A. . P. T. .E . R. . 4. .. .L .O . C. .A . T. .I N. .G . .A . .R . T. I. F. A. .C . T. .S . W. . I.T . H. . M. . A. .V . E. .N . .A . N. .D . .H . T. .T . P. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2. .6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1. LOCATING HTTP ARTIFACTS 26
4.2. LOCATING MAVEN ARTIFACTS AT BUILD TIME 27
4.3. LOCATING MAVEN ARTIFACTS AT RUN TIME 29
.P .A . .R . T. .I .I .. O. .S . G. .I .B . U. .N . D. .L . E. . D. .E .P . L. .O . Y. .M . .E .N . T. . M. . O. .D . E. .L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4. .3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.C .H . A. . P. T. .E . R. . 5. .. I. N. .T . R. .O . D. .U . C. .T .I .O . N. . T. .O . .O . S. .G . I. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4. .4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1. RED HAT JBOSS FUSE 44
5.2. OSGI FRAMEWORK 45
5.3. OSGI SERVICES 46
5.4. OSGI BUNDLES 48
.C .H . A. . P. T. .E . R. . 6. .. B. . U. .I L. D. . I.N . G. . A. .N . .O . S. .G . I. B. .U . .N . D. .L .E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5. .0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1. GENERATING A BUNDLE PROJECT 50
6.2. MODIFYING AN EXISTING MAVEN PROJECT 51
6.3. PACKAGING A WEB SERVICE IN A BUNDLE 53
6.4. CONFIGURING THE BUNDLE PLUG-IN 55
.C .H . A. . P. T. .E . R. . 7. .. D. .E . P. .L .O . .Y . I.N . G. . A. .N . .O . S. .G . I. B. .U . .N . D. .L .E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6. .0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1. HOT DEPLOYMENT 60
7.2. MANUAL DEPLOYMENT 60
7.3. LIFECYCLE MANAGEMENT 62
7.4. TROUBLESHOOTING DEPENDENCIES 64
.C .H . A. . P. T. .E . R. . 8. .. .D . E. P. .L . O. .Y . I.N . G. . F. .E . A. .T .U . .R . E. S. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6. .8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1. CREATING A FEATURE 68
8.2. DEPLOYING A FEATURE 72
.C .H . A. . P. T. .E . R. . 9. .. D. . E. P. .L . O. .Y . I.N . G. . A. . P. .L . A. .I N. . J. .A . R. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7. .5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1. BUNDLE TOOL (BND) 75
9.2. CONVERTING A JAR USING BND 76
9.3. CONVERTING A JAR USING THE WRAP SCHEME 79
.C .H . A. . P. T. .E . R. . 1. 0. .. O. . S. G. .I . B. .U . N. .D . L. E. . T. .U . T. .O . R. .I A. .L . S. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8. .2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1. GENERATING AND RUNNING AN EIP BUNDLE 82
1
Red Hat JBoss Fuse 6.2.1 Deploying into Apache Karaf
10.2. GENERATING AND RUNNING A WEB SERVICES BUNDLE 84
.P .A . .R . T. .I .I I.. .W . .A . R. . D. .E . P. .L .O . .Y . M. .E . N. .T . .M . O. .D . E. .L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8. .7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.C .H . A. . P. T. .E . R. . 1. 1.. .B . U. . I.L .D . I. N. .G . .A . .W . .A . R. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8. .8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1. MODIFYING AN EXISTING MAVEN PROJECT 88
11.2. BOOTSTRAPPING A CXF SERVLET IN A WAR 91
11.3. BOOTSTRAPPING A SPRING CONTEXT IN A WAR 92
.C .H . A. . P. T. .E . R. . 1. 2. .. D. .E . P. .L .O . .Y . I.N . G. . A. . W. . A. .R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9. .4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1. CONVERTING THE WAR USING THE WAR SCHEME 94
12.2. CONFIGURING THE WEB CONTAINER 95
.P .A . .R . T. .I .V . .. O. .S .G . I. .S .E . R. .V . I. C. E. . L. .A . Y. .E .R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9. .7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.C .H . A. . P. T. .E . R. . 1. 3. .. O. .S . G. .I .S . E. .R . V. .I C. .E . S. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9. .8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.1. THE BLUEPRINT CONTAINER 98
13.2. PUBLISHING AN OSGI SERVICE 112
13.3. ACCESSING AN OSGI SERVICE 116
13.4. INTEGRATION WITH APACHE CAMEL 120
.C .H . A. . P. T. .E . R. . 1. 4. .. J. .M . S. . B. .R . O. .K . E. .R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 2. .3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.1. WORKING WITH THE DEFAULT BROKER 123
14.2. JMS ENDPOINTS IN A ROUTER APPLICATION 124
.A . P. .P .E . N. .D . I. X. . A. .. .U . R. .L . H. . A. .N . D. .L .E . R. .S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. 2. .8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.1. FILE URL HANDLER 128
A.2. HTTP URL HANDLER 128
A.3. MVN URL HANDLER 128
A.4. WRAP URL HANDLER 131
A.5. WAR URL HANDLER 132
.A . P. .P .E . N. .D . I. X. . B. .. .O . S. .G . I. B. .E . S. T. . P. .R . A. .C . T. .I C. .E .S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 3. .5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.1. OSGI TOOLING 135
B.2. BUILDING OSGI BUNDLES 136
B.3. SAMPLE POM FILE 141
.A . P. .P .E . N. .D . I. X. . C. .. .P .A . .X . -.E . X. .A . M. . .T .E . S. .T .I .N . G. . F. R. .A . .M . E. .W . .O . R. .K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. 4. .3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C.1. INTRODUCTION TO PAX-EXAM 143
C.2. SAMPLE PAX-EXAM TEST CLASS 148
.I N. .D . E. .X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5 . 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
Table of Contents
3
Red Hat JBoss Fuse 6.2.1 Deploying into Apache Karaf
PART I. THE RED HAT JBOSS FUSE CONTAINER
Abstract
The Red Hat JBoss Fuse container is a flexible container that supports a variety of different
deployment models: OSGi bundle deployment and WAR deployment. The container is also integrated
with Apache Maven, so that required artifacts can be downloaded and installed dynamically at deploy
time.
4
CHAPTER 1. RED HAT JBOSS FUSE OVERVIEW
CHAPTER 1. RED HAT JBOSS FUSE OVERVIEW
Abstract
Red Hat JBoss Fuse is a flexible container that allows you to deploy applications in a range of different
package types (WAR or OSGi bundle) and has support for both synchronous and asynchronous
communication.
1.1. RED HAT JBOSS FUSE CONTAINER ARCHITECTURE
Overview
Figure 1.1, “Red Hat JBoss Fuse Container Architecture” shows a high-level overview of the Red Hat
JBoss Fuse container architecture, showing the variety of deployment models that are supported.
Figure 1.1. Red Hat JBoss Fuse Container Architecture
e R
l A
d
W
n
u
B
Deployment models
Red Hat JBoss Fuse is a multi-faceted container that supports a variety of deployment models. You can
deploy any of the following kinds of deployment unit:
OSGi bundle
An OSGi bundle is a JAR file augmented with metadata in the JAR's META-INF/MANIFEST.MF file.
Because the Red Hat JBoss Fuse container is fundamentally an OSGi container, the OSGi bundle is
also the native format for the container. Ultimately, after deployment, all of the other deployment
unit types are converted into OSGi bundles.
WAR
A Web application ARchive (WAR) is the standard archive format for applications that run inside a
Web server. As originally conceived by the Java servlet specification, a WAR packages Web pages,
JSP pages, Java classes, servlet code, and so on, as required for a typical Web application. More
generally, however, a WAR can be any deployment unit that obeys the basic WAR packaging rules
(which, in particular, require the presence of a Web application deployment descriptor, web.xml).
Spring framework
The Spring framework is a popular dependency injection framework, which is fully integrated into the
JBoss Fuse container. In other words, Spring enables you to create instances of Java objects and wire
5
Red Hat JBoss Fuse 6.2.1 Deploying into Apache Karaf
them together by defining a file in XML format. In addition, you can also access a wide variety of
utilities and services (such as security, persistence, and transactions) through the Spring framework.
Blueprint framework
The blueprint framework is a dependency injection framework defined by the OSGi Alliance. It is
similar to Spring (in fact, it was originally sponsored by SpringSource), but is a more lightweight
framework that is optimized for the OSGi environment.
OSGi core framework
At its heart, Red Hat JBoss Fuse is an OSGi container, based on Apache Karaf, whose architecture is
defined by the OSGi Service Platform Core Specification (available from
http://www.osgi.org/Release4/Download). OSGi is a flexible and dynamic container, whose particular
strengths include: sophisticated management of version dependencies; sharing libraries between
applications; and support for dynamically updating libraries at run time (hot fixes).
For more details about the OSGi framework, see Chapter 5, Introduction to OSGi.
Red Hat JBoss Fuse kernel
The JBoss Fuse kernel extends the core framework of OSGi, adding features such as the runtime
console, administration, logging, deployment, provisioning, management, and so on. For more details,
see Section 5.1, “Red Hat JBoss Fuse”.
1.2. DEPLOYMENT MODELS
09/27/12
Reordered to make OSGi more prominent
Overview
Although Red Hat JBoss Fuse is an OSGi container at heart, it supports a variety of different
deployment models. You can think of these as virtual containers, which hide the details of the OSGi
framework. In this section we compare the deployment models to give you some idea of the
weaknesses and strengths of each model.
Table 1.1, “Alternative Deployment Packages” shows an overview of the package types associated with
each deployment model.
Table 1.1. Alternative Deployment Packages
Package Metadata Maven Plug-in URI Scheme File Suffix
Bundle MANIFEST.MF maven- None .jar
bundle-
plugin
WAR web.xml maven-war- war: .war
plugin
OSGi bundle deployment model
6