This post originated from an RSS feed registered with Java Buzz
by Marc Logemann.
Original Post: My plans for Netversys 2.0 -> OSGi compliance
Feed Title: Logemann Blog
Feed URL: http://www.logemann.org/blojsom/blog/default/?flavor=rss2
Feed Description: Marc's thoughts on Java and more
While brainstorming what non-business related features the next major version of our logistics product should have, i ended up with one big word: OSGi. And not because its one of the cool buzzwords in javaland these days but because our software is definitely very well suited for having modules which should be installed and updated seperately.
Right now our app is quite monolithic. If i want to upgrade some UPS related things, i need to ship a complete new version of our software. Same for other carriers like DHL or Fedex. With a nice plugin system, i could just provide a new UPS plugin. Of course i could also go by just using different JARs in WEB-INF/lib or use JPF but since our app is relying on spring, i want to wait for their upcoming OSGi support which will make it perhaps in spring v2.1.
At this point i dont know too much about OSGi. I just read the Spring-OSGi spec and what i understood is quite promising. But before i start with that, i need to upgrade to Spring 2.x first, but i dont expect much problems there (in contrast to my upcoming kodo migration). So it seems that my life wont get boring anytime soon.
Previous Topic
