Video: Part 2 of an Introduction to the NetBeans APIs
Part 1 focused on the problem statement, the runtime container, and the Module System API. Now, in part 2, we will look at the next of the top 10 NetBeans APIs: the Lookup API.
Related Links:
- NetBeans Platform Homepage
- NetBeans API Javadoc
- Tim Boudreau's Selection Management Tutorial
- Geertjan's blog on Top 10 NetBeans APIs
Download for off-line viewing here.
- Login or register to post comments
- 5613 reads
- Printer-friendly version
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)










Comments
mxb replied on Sun, 2008/11/16 - 6:51pm
Hi Geertjan
Many thanks for this second episode. I found it very helpful for understanding how service providers and dependencies are handled in the Netbeans Platform. I skipped that portion that dealt with the Java 6 ServiceProvider example, not having access to Java 6 at the moment. In any case perhaps it would be better for the screencast to present the Netbeans approach first and then have a brief comparison with the Java 6 approach in the closing section.
Michael
patsanchotok replied on Tue, 2009/05/12 - 1:02am
Not bad, right? Methods for adding dependencies, entries in the layer.xml file, attributes, bundle settings, and so on. Really cool. An entire framework for NetBeans API wizards. So, even though it might take a bit of work, at least initially, to enhance these wizards, once you've done so you'll never need to create boilerplate code again. After all, the basis of every editor palette is the same, the basis of every OpenSupport implementation is the same. And there are many such scenarios that are identical for each module. And how many times have you had to create those by hand? Seems like a lot of unnecessary work. Invest a little bit of time in enhancing the apisupport/project module for your environment by letting the wizards generate your most commonly typed code and then you'll be able to use them to generate more and more of the code you need from that point on. After all, people using these wizards are NetBeans API implementors anyway, so it's not such a stretch to suggest that those who want to use the NetBeans APIs can hone their skills by extending the existing code generators (and adding new ones) for their specific subset of boilerplate code. Hence, my suggestion is, whenever you find yourself typing the same lines of code over and over again, you need to wonder whether you shouldn't try to enhance one of the wizards to do that work for you. Yes, you'll have a customized version of the apisupport/project module, which means that when a new release of that module comes out with NetBeans IDE, you'll need to manually upgrade or do something if you want to make use of new enhancements in the official release, but that's life. Every advantage has a disadvantage.
canadian drugstore rx drugs canadian pharmacy viagra
PhilEdward replied on Fri, 2009/06/26 - 6:09am
PhilEdward replied on Fri, 2009/06/26 - 6:10am
jiji530 replied on Fri, 2009/06/26 - 8:07pm
KrisBin replied on Sat, 2009/06/27 - 10:29am