In 2005 I assessed The Netbeans Platform as a candidate for developing client applications.
As always when examining a new Java™ API and related software tutorials and docs, I fired up MagicDraw™ UML and did some reverse-engineering (in this case of the Java sources) into graphical UML™, to get a feel for the API. And as usual, I used additional «wrapper» Components in my diagrams (rather than just relatively graphically unstructured "freestyle" class diagrams) to logically and graphically group related model elements. Some UML diagram examples are made available here.
These diagrams are much larger than I recommend, they need to be progressively "divided and conquered" into related diagrams that can be navigated in the UML project via model element hyperlinks. I usually start like this then split the diagram into related "class collaborations". Also, I do not usually recommend showing so many methods/operations of multiple classes and interfaces. These are nevertheless very good examples of the power of UML diagramming with logical «wrapper» Components, in fact they capture my "wrapper" process nicely.
