A practical guide to mixing java EE and OSGi - Jfokus

More documents

Recommendations

Info

What do we need? design consequences High-level enterprise APIs Architectural focus on modularity let’s not reinvent the wheel Runtime dynamic module framework Right now, OSGi is the only option
OSGi is the de-facto standard module system for Java What about Jigsaw? OSGi != modularity
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: How to deal with Runtime dynamics M
Page 23 and 24: OSGi is the de-facto standard modul
Page 25 and 26: OSGi vs. Java EE
Page 27 and 28: Java EE: high level APIs OSGi vs. J
Page 29 and 30: Option 1 - OSGi in Java EE App Serv
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

Create successful ePaper yourself

Delete template?

Save as template?