Java Reference
In-Depth Information
Apache Aries
Blueprint
container
Container-
managed JPA
Container-
managed JTA
Application
management
Application server
(Geronimo - selected parts)
JPA
(OpenJPA)
Web container
(Jetty)
Automatic bundle installer
(Felix Fileinstall)
Database
(Derby)
OSGi Framework
(Equinox)
Figure 2.2
As well as Apache Aries components, the Aries sandbox stack includes an OSGi frame-
work, a database, web container, JPA and JTA implementations, and a few pieces of the Geronimo
application server.
What do all those JARs do?
If you count the JARs in the target directory, you may be surprised by how many
there are. Does it take 35 JARs to run an OSGi web application? No. You could get
away with a handful of bundles, but then you'd need to download a few more to get
the Blueprint dependency injection going, and then a few more once you start play-
ing with persistence in chapter 3. We thought it was probably easier to download ev-
erything at once!
If you're the sort of person who likes to take everything apart and then put it back
together again, we've got a detailed guide to what's what in the Aries sandbox in
appendix B.
Launch the
OSG
i framework using the
OSG
i
JAR
:
cd target
java -jar org.eclipse.osgi-3.7.0.v20110613.jar -console
(Depending on which release you're using, the version of the
OSG
i
JAR
may be differ-
ent.) The
-console
argument is important, because it brings up the
OSG
i console that
allows you to see what
OSG
i bundles are active and start, stop, and install new bundles.
Type
ss
to see a list of all the bundles in the framework (see figure 2.3). The
ss
stands for “short status” and provides a high-level view of the bundles available in the
