I for one, welcome our new Spring Overlords

0 views
Skip to first unread message

Aaron Korver

unread,
May 2, 2008, 2:08:53 PM5/2/08
to CIJUG
http://www.infoq.com/news/2008/04/springsource-app-platform

So everyone get cracking on your OSGi modules.  Throw out your Websphere/Weblogic/Oracle/JBoss servers.  Delete your EJBs and EAR files.  For a new day has dawned upon us thanks to our new Spring Overlords.

On a serious note, is this innovation or simply "Spring doesn't want to place nicey nice" with the regular vendors?

And...

How many times will we as developers be forced to learn a new magical framework that will magically fix all of our problems?  The problems don't seem to change much, simply the coat of paint that vendor X gives it changes.

Aaron Korver

unread,
May 2, 2008, 2:14:42 PM5/2/08
to CIJUG

Dan Mullins

unread,
May 2, 2008, 2:56:57 PM5/2/08
to Central-Iowa-J...@googlegroups.com
I think it's a great idea actually.

It introduces OSGI as an enterprise platform and gives Java an Adobe AIR competitor. You could deploy thin client apps to a person's desktop and operate in a connected/disconnected state.

Aaron Korver <aaron....@gmail.com> wrote:

Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.

Aaron Korver

unread,
May 2, 2008, 3:15:59 PM5/2/08
to Central-Iowa-J...@googlegroups.com
Is OSGi really something that should be "enterprise"?  I've been completely ignorant of OSGi, but today it broke my rule that states "Ignore all buzzwords/technology unless it hits my radar more than 5 times in a day".  So now I'm looking at it and wondering why/how it will provide solutions that other tools in my toolbox don't already provide.

Coming out to the market with a hammer that I can change the head on is an interesting product, but it doesn't mean I'm going to dump my claw hammer and my finish hammer and jump to this new thing.  Why?  Because it doesn't do anything my current tools can't do.

So please, forgive my ignorance.  I really do want to welcome our Spring/OSGi Overlords, but I need some education first on why it will be such a great idea.

Dan Mullins

unread,
May 2, 2008, 3:53:31 PM5/2/08
to Central-Iowa-J...@googlegroups.com
I can't do OSGI justice in an e-mail, you'll have to do your own research on that. But here's why I think it's pretty cool.

It introduces the concept of "services" at a java level. Instead of deploying one war with built-in services for talking to the database, you rely on a database OSGI "bundle" being available in your runtime environment. The bundle has an id, a version number, and a series of services it exposes to the collective runtime. It is also self-contained with it's own jars and classloader.This way, your UI doesn't package the service code and all of its dependencies, it just relies on it being there. Version 1.0 may retrieve the data from the database, version 2.0 may use a web-service. Both can co-exist in the same runtime, but won't have classpath conflicts since they have their own classloaders.

What Spring did (from my understanding), is took an OSGI runtime and added a bunch of spring bundles. From an enterprise community, it's impressive to think about how this could be used. A whole runtime full of services just waiting to be consumed. No web-services, no RMI and no XML. Instead of creating a service that accesses some backend system and using a tool like Ivy to pull him and all his dependencies in. You could write that same system as an OSGI bundle, deploy it, and every application that needs it can reference it. If you're not ready to switch everyone over, keep the last 3 versions out there and let people upgrade as they want.
Reply all
Reply to author
Forward
0 new messages