|
From: Lieven D. <lie...@ji...> - 2008-07-04 10:25:46
|
Hi guys, Been reading all the posts here and been comtemplating on OSGi. And frankly, as a business application developers, I really don't see the additional benefit of a modular system on a GUI level. Perhaps I'm thick, I don't know, but I really can't find a reason to provide a modular system on a GUI framework system. Most application I come in contact with don't have a modular design (actually, that's incorrect, but not in the modular sense we're talking about here). Enterprise custom-built application don't need plugin functionality (although it could be handy on a development level, granted). They almost always see their thick-client gui as a entire module (in the sense we're talking about here), which might be split up in different modules (in the more traditional way, for development purposes). Don't get me wrong, I do see OSGi as a good thing, but for clearly defined concerns (dao, service, webservice, domain (although disputable, who would want to take down a POJO layer...) and webstart GUI as a single module)... Using OSGi for GUI just seems overkill, could anyone give me an example on how he or she would split up his GUI application, 'cause that would be great. Please enlighten me, let me see the OSGi light :). Kind regards, Lieven > ---------------------------------------------------------------------- > --- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Springframework-rcp-dev mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev |