Uploaded byGuillaume Nodet
Jug Poitou Charentes - Apache, OSGi and Karaf
The document discusses Apache Karaf, OSGi, Blueprint and related topics. It provides an overview of the Apache Software Foundation and its role in open source projects like OSGi. It then summarizes OSGi and how it addresses modularity challenges in Java. Finally, it introduces Blueprint for dependency injection in OSGi and Apache Karaf as an OSGi-based runtime.
Jug Poitou Charentes - Apache, OSGi and Karaf
- 1. Apache, OSGi, Blueprint andKaraf Guillaume Nodet January 20, 2011
- 2. Your presenter: Guillaume Nodet FuseSource http://fusesource.com Apache Software Foundation Member, VP Apache Karaf, PMC Member of ActiveMQ, Aries, Camel, CXF, Felix, Geronimo, Karaf, Mina, Ode, ServiceMix Co-creator of ServiceMix, Karaf, Mina SSHD Member of the OSGi EEG
- 3. Overall agenda The ApacheSoftware Foundation OSGi overview OSGi at the ASF Quick Blueprint intro Apache Karaf
- 4. The Apache Software Foundation What it is and how it works...
- 5. Schedule What is the ApacheSoftware Project Foundation Management A bit of The Foundation history infrastructure Meritocracy Other foundation The Foundation entities structure Conclusion Roles
- 6. What is theApache Software Foundation? Non-profit organization Open, collaborative software development Independent legal entity for donations Means for individuals to be sheltered from legal suits Protect the ‘Apache’ brand
- 7. History HTTPD web serverfrom the NCSA Community to support it Developers called themselves the “Apache Group” ASF created in 1999
- 8. Meritocracy Not initiated bya single person More people attracted and started contributing When a person “earned” the merit, access to the repository was granted Scales well as newcomers are volunteers and no power to steal
- 9. Foundation structure Projectsare delegated authority and are self-governing Board of Directors Project Management Committees
- 10. Board of Directors Manageand oversee the corporation, its assets and resources Technical authority assigned to PMC Nine individuals (members), elected every year
- 11. Project Management Committees Established and terminated by resolution of the Board One officer (VP) appointed by the Board (PMC chair). Establish rules, report to the board, perform administrative tasks PMC oversee legal aspects and community health
- 12. Officers Oversee the day-to-dayaffairs Elected by the Board
- 13.
- 14. Project Management Collaborative andconsensus-based pocess No single set of rules between PMCs
- 15. Project Management (cont) Communication Operation Documentation Individuals Decision making Confidentiality Philosophy vs public
- 16. The Incubator fitering (nontechnical) proposals of new projects help creation / infrastrucure mentor the incubated community to become open and meritocratic evaluate the maturity for graduation
- 17. The Incubator (cont.) working code base copyright donation sponsoring member increase diversity (long term stability, variety of technical visions)
- 18. Other entities Infrastructure team Attic,Labs, Legal Affairs, Public Relations, Conferences ...
- 20.
- 21. OSGi Alliance Formerly knownas the Open Services Gateway Initiative Industry consortium Defines OSGi Service Platform Serveral expert groups
- 22. OSGi Architecture Overview
- 23. OSGi Framework Component oriented Serviceoriented architecture Run multiple applications Single VM Separate class loader per bundle Dynamic
- 24. OSGi Framework layers
- 25. OSGi momentum OSGi technologyhas moved beyond original target domain Initial success story was Eclipse RCP More recent success stories in enterprise scenarios
- 26. OSGi Specifications OSGi R4.2released in Sept/09 Blueprint, Remote Services, Web Applications, JNDI, JTA, JDBC, JPA Next Core release in Q1 2011 Next Enterprise release in Q1 2012 Subsystems, OBR ...
- 27.
- 28. Standard Java Modularity Limitations Limited scoping mechanism Simplitic version handling Implicit dependencies Split packages by default Low-level support for dynamics Unsophisticated consitency model Missing module concept
- 29. OSGi Framework modularity support Resolvesnearly all deficiencies OSGi bundles as a boundary for a module Bundle metadata explicitly declares versioned dependencies Framework automatically manages bundle code dependencies Framework enforces sophisticated consistency rules for class loading
- 30.
- 32. OSGi at theASF Overview of the various projects
- 33. 88 Top LevelProjects More then 40 incubating projects
- 34. Classification Non Java Non OSGiaware OSGi aware (provide OSGi bundles) OSGi based
- 35. OSGi Based Aries Felix Incubator Karaf Ace ServiceMix Celix Sling Clerezza Geronimo (i.p.)
- 36. OSGi Aware Abdera Directory (i.p.) ActiveMQ Harmony Axis HttpComponents Camel Mina Commons OpenEJB CXF OpenJPA DB Synapse
- 38.
- 39. Overview Dependency injection /IOC Handle legacy code Handle OSGi dynamics Hide the OSGi API
- 40. Configuration Extender pattern XML resources Metadata Blueprint Bundle Metadata XML Blueprint Extender
- 41. Simple example <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0”> <service interface=“org.poitoucharentesjug.User”> <bean class=“org.poitoucharentesjug.impl.UserImpl”> <argument value=“gnodet” /> </bean> </service> </blueprint>
- 42. Managers manager bean service-reference service reference reference-list
- 45. Overview Apache Karaf isa small OSGi based runtime which provides a lightweight container onto which various components and applications can be deployed.
- 46. Karaf Console Poweful commandline shell Highly extensible SSH access
- 47. Logging Support multiple APIs OSGi, JCL, JUL, Log4j, Slf4j Uses a single back-end Dynamic reconfiguration through ConfigAdmin Shell integration
- 48.
- 49. Provisionning Features concept Maven integration(plugin, url handler) Drives OSGi SubSystems specification
- 50. Other OS integration Instances management JAASbased security
- 52.
Editor's Notes
- #2 \n
- #3 \n
- #4 \n
- #5 \n
- #6 \n
- #7 \n
- #8 \n
- #9 \n
- #10 The Foundation structure\nAs the Apache Web Server started to grow in market share and popularity, due to synergy of its technical merit and to the openness of the community behind the project, people started to create satellite projects. Influenced by the spirit of the community they were used to, they adopted the same traditions of community management.\nSo, by the time the ASF was created, there were several separate communities, each focused on a different side of the "web serving" problem, but all united by a common set of goals and a respected set of cultural traditions in both etiquette and process.\nThese separate communities were referred to as "projects" and while similar, each of them exhibited little differences that made them special.\nIn order to reduce friction and allow for diversity to emerge, rather than forcing a monoculture from the top, the projects are designated the central decision-making organizations of the Apache world. Each project is delegated authority over development of its software, and is given a great deal of latitude in designing its own technical charter and its own governing rules.\nAt the same time, the cultural influence of the original Apache group was strong and the similarities between the various communities are evident, as we'll see later.\nThe foundation is governed by the following entities:\nBoard of Directors (board) governs the foundation and is composed of members.\nProject Management Committees (PMC) govern the projects, and they are composed of committers. (Note that every member is, by definition, also a committer.)\n\n
- #11 \n
- #12 \n
- #13 \n
- #14 \n
- #15 \n
- #16 \n
- #17 \n
- #18 \n
- #19 \n
- #20 \n
- #21 \n
- #22 \n
- #23 \n
- #24 \n
- #25 \n
- #26 \n
- #27 \n
- #28 \n
- #29 \n
- #30 \n
- #31 \n
- #32 \n
- #33 \n
- #34 \n
- #35 \n
- #36 \n
- #37 \n
- #38 \n
- #39 \n
- #40 \n
- #41 \n
- #42 \n
- #43 \n
- #44 \n
- #45 \n
- #46 \n
- #47 \n
- #48 \n
- #49 \n
- #50 \n
- #51 \n
- #52 \n
- #53 \n