A practical guide to mixing java EE and OSGi - Jfokus

More documents

Recommendations

Info

How? - 3 options #1#2 OSGi as core architecture with EE APIs published as services Hybrid solution using an injection bridge #3 OSGi a la carte
Option 1 - OSGi in Java EE App Servers OSGi bundles as your core programming model Java EE APIs available from within bundles use app server capabilities like clustering, data sources, etc. the (near) future!
Page 1 and 2: Modular Java EE in the cloud A prac
Page 3 and 4: Bert Ertman Fellow at Luminis in th
Page 5 and 6: This leads to a number of challenge
Page 7 and 8: Modularity is the answer
Page 9 and 10: What we learned about OO design in
Page 11 and 12: How to prevent coupling in a code b
Page 13 and 14: But how to make imp lemen tation su
Page 15 and 16: Ok, but how to create an instance o
Page 17 and 18: Design time modularity Divide and c
Page 19 and 20: How to deal with Runtime dynamics M
Page 21 and 22: OSGi is the de-facto standard modul
Page 23 and 24: OSGi is the de-facto standard modul
Page 25 and 26: OSGi vs. Java EE
Page 27: Java EE: high level APIs OSGi vs. J
Page 31 and 32: Web Application Bundle (WAB) mywab.
Page 33 and 34: EJB Bundles manifest.mf Bundle-Name
Page 35 and 36: How are the app servers doing? App
Page 37 and 38: Example
Page 39 and 40: What about deployment?
Page 41: Apache ACE
Page 44 and 45: What have we learned? You’ve seen
Page 46: Cloud provisioning http://ace.apach

A practical guide to mixing java EE and OSGi - Jfokus

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?