The DS tooling in Eclipse is reasonably comprehensive.  See
    http://eclipsesource.com/blogs/2009/03/03/osgi-declarative-services-tooling/
I've been using DS and this tooling for some time now and it does pretty much all that is needed. The set of refactorings and validations available increases everyday.  One thing that was mentioned was the lack of support for multiple components in one XML file.  Currently this is true.  Perhaps I have just adapted or just don't see this as a problem.  When starting out with DS (this was before the DS tooling) my first inclination was to put all components for a bundle in one file. The result was simpler management of the manifest.mf.  Great.  The downsides were; it does not save on XML and it was then harder to refactor my bundles and move components around.  This approach also lets you see what components are in a bundle without having to look at the XML (assuming you use decent names for the files).

Everyone is different but for my money I prefer putting components in individual files. I program with DS pretty much every day and honestly have little idea what the XML looks like and certainly have not edited it directly in quite some time.  Repo stats may show me as an XML programmer but statistics can be deceiving.

my 2c...

Jeff
Jeff McAffer | CTO | EclipseSource | +1 613 851 4644
[email protected] | http://eclipsesource.com


Aaron Zeckoski wrote:
I was (and am) concerend about living in xml hell as well. Nothing is
quite so much fun as looking at my developer profile in ohloh and
finding out I am apparently an xml programmer primarily... sigh. That
said, there are some plugins I have used that help with this
(http://felix.apache.org/site/apache-felix-maven-scr-plugin.html) but
if someone knows of a nice blog entry or listing of tools related to
DS I would greatly appreciate a link or two (and probably others might
as well).
Thanks!
-AZ

On Thu, Apr 30, 2009 at 11:41 PM, Scott Lewis <[email protected]> wrote:
  
Hi Eugen,

Eugen Reiswich wrote:
    
Hi Neil,

<stuff deleted>

Is DS really the only way? I have downloaded Eclipse M6 and tested the
DS-Editor. Well, how do I say it polite? If I have 2, 3 or even more
components in one bundle that require OSGi services I have to create (if I
got it right) 2, 3 or even more XML files with
service-component-descriptions. This sounds like XML-hell.
      
Although I sympathize/empathize, I don't think DS constitutes XML-hell.

DS is not the only way, but it does manage inter-service dependencies very
effectively IMHO.  I've been using it rather heavily recently, and after
some initial learning time for me, I now consider it very helpful (and I was
skeptical about xml hell as well).

And the DS tooling in Eclipse 3.5 is still very early...it will
improved/extended quickly I expect.  Even so, I've found it very helpful in
its current state (although still have plenty of suggestions for
improvements in the tooling).

In any event, I wouldn't dismiss DS too quickly, if that's your inclination.

My $0.02.

Scott


_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev

    



  
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev

Reply via email to