...
The idea with the first chunk of our Fedora-OSGi work was to a) prove that Fedora can be packaged as a complete OSGi bundle, and b) begin OSGi-fying some of the key pieces that Fedora uses under the hood. To that end, Eddie experiemented and had some success with building Fedora as an OSGi bundle, and started doing the same for Mulgara. Chris successfully changed Akubra's plugins to be OSGi bundles and has gained experience in making existing artifacts OSGi-friendly.
Bill and Andrew are actively using OSGi for the "service" portion of DuraCloud, but noted that there is a significant learning curve and a new set of dependency issues to be concerned with, similar to the "growing pains" we experienced in the transition to Maven.
Those of us with some OSGi experience agreed that OSGi still represents a promising direction for Fedora, but there are still a lot of hurdles to getting there. Like maven, these hurdles will become shorter with time, as Java-OSGi adoption increases and the community around it grows.
During this discussion, we noted again that moving toward OSGi is not incompatible with using Spring for dependency injection. The latter seems to be a more tractable goal for the time being, with more immediate payoff. We agreed to:
Document best practices for being "OSGi Friendly"- In the short-term, move to Spring for dependency injection (Fedora modules = spring beans)
- Keep the long-term goal of having a Fedora OSGi bundle that can be used by other apps
To drive this work forward, we identified:
- Lead:
Chris - Contrib:
Dan, Andrew, Asger
High Level Storage
Aaron
Semantic Web and Linked Data
Steve
WebDAV
Kai
Tuesday
| Panel | ||
|---|---|---|
| ||
...