11. Qwylt
APIs for interacting with modules
SPIs for building module systems
Platform for sharing classes between
module systems
12. Pros
Seems to offer interop between OSGi and
Jigsaw at runtime
Oracle claim to have implemented 90% of
OSGi on Qwylt (“Lyra”), based on Felix
code.
13. Cons
No common module format
Library authors targeting both module
systems will have to compile, build and
test twice.
23. Modular Architecture
Kirk Knoernschild, Neil Bartlett
Tutorial format: high level architecture
from Kirk, low level details from me
Focus on DS and simplicity seemed to
go down well
26. OSGi Shells
Robert Dunne (Paremus)
Current situation is annoying for
writers of tutorials & other docs
Existing shells are underpowered
RFC 147 describes the new standard
shell, GoGo is a prototype
27. Paremus Nimble
Shell and provisioning system
Understands service dependencies, not
just imports/requires.
Not open source, but free to use
(renewable licence)
33. Graham Charters (IBM)
“Enabling the OSGi development model
in the enterprise...”
“Enabling the OSGi development model
in the enterprise...”
and
“Enabling the OSGi development model
in the enterprise...”
35. ScalaModules
A DSL to ease development with OSGi
services
Complements DS, Blueprint etc
Gives access to full power of low-level
APIs...
but much easier & safer to use.
36. ScalaModules
Size of the core Scala library was
discussed: 4Mb
Clearly creates a barrier to adoption of
Scala
Needs to be modularised!
40. OSGi Cloud Workshop
Lots of participants!
Key Question:
What needs to be specified, vs “value
added” features that vendors may
implement?
Likelihood of a new “Cloud Expert
Group” in the near future?