« Python Turbo Gears and Jython interop | Main | Advertising, content networks, domains, registrars, and a few other dirty little secrets on the web »
January 7, 2008
OSGi and server side Java : Implications and how does it actually work
OSGi is slowly but surely moving into Java server-side territory and a few other SOA product lines in the industry. Among the most noted, you will find a few of the earliest Java Application Servers now being tagged 'OSGi compliant' or 'OSGi based', in addition, popular Java frameworks like Spring have also blossomed OSGi integration sub-projects. But what are the actual implications behind OSGi ? And more importantly how can you work with it ? This entry covers an article I recently wrote on the subject which includes a hands-on OSGi example, as well as the potential implications OSGi will have on the overall Java and SOA ecosystem.
| [Entry continues to the left and below ad ] |
The article starts off by covering OSGi root's and why it was seen as a good choice for server-side Java and Service Orientated Architecture (SOA) designs, followed by a step by step deployment of an OSGi project using the Apache Software foundation implementation named Felix, ending with OSGi's implications to other Java initiatives like Java 7, Java Enterprise Edition and other JSR's.
You can read the intro at OSGi on the Server Side and the complete article on BEA's Dev2Dev site : An Introduction to OSGi on the Server Side .
| [Comments below ad ] |
Posted by Daniel at January 7, 2008 12:29 PM
Comments
Daniel, I enjoyed the article. I thought you did a great job explaining a broad-ranging and complex topic. I started working with OSGi around 2000/2001 in the embedded space. I then focused on the server-side and left OSGi behind. It's exciting to see it extend to the server side and other areas like Eclipse.
Posted by: James Bayer at January 23, 2008 2:21 PM
Post a comment
Track back Pings
Track Back URL for this entry:
http://www.webforefront.com/mtblog/mt-tb.cgi/72.
[Any other Reader]
