News from Jun 17, 2009
|
Browse Space : Pages • News • Labels • Attachments • Bookmarks • Mail • Activity • Advanced |
|
|
June 2009 |
|
||||
|---|---|---|---|---|---|---|
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 7 | 8 | 9 | 10 | 11 | 12 | 13 |
| 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| 28 | 29 | 30 | ||||
DZone: In general, tools for OSGi development seem sparse. Do you have any recommendations on tools or frameworks that aid bundle development, management, or runtime environment setup? Do you have a preferred OSGi development stack?
Craig: I'm a huge fan of the work done on the OPS4J Pax projects. They offer several great tools for working with OSGi, including Pax Construct, a script-driven approach to developing OSGi projects that is quite similar to working with frameworks like Rails and Grails. and a runtime setup tool called Pax Runner that's great for bootstrapping an OSGi framework with a selection of bundles. I can't imagine developing OSGi bundles without Pax Construct or starting an OSGi-based application without Pax Runner.