I don't get the naming policy...

[mmo]

I am drawing a component diagram where an Object (the "Web-server") contains several components ("WebServices") each containing one or more classes ("servlets").
That hierachy is also correctly shown in the left hand side Project browser tree (i.e. the hierachy and containment relations are correct).
What I don't get is the names being displayed. Some servlets are labeled <Object>::<component>::<classname> while others are only labeled <Object>::<classname>, i.e. the <component>:: fragment is missing. And that's even though - as I double checked! - they are contained in the component. I even modified the name to make sure, it's not just some name refresh problem.

Why is that so? Why are some objects labeled one way and others differently?

And - since we are at it: I would actually prefer to omit these prefixes altogether, i.e. I would prefer to have the classes just being labeled with their name and no container. Can one achieve that? Neither "Properties" nor "Feature visibility" nor any other context menu entry seems to allow to control this...

Michael

[Geert Bellekens]

Michael,

There is no reason why you would create your classes inside a servlet that is inside a web-server.
After all you deploy your classes on a component, but you don't have to create them in one.
In 99% of the cases nested classes shouldn't be nested at all.

Geert

[mmo]

The diagram will be part of the hand-over program documentation and I want to make clear which servlet class actually implements a given component.

But regardless of whether that makes sense in UML terms, I still don't understand why some components are labeled with their entire hierarchy and others aren't.

Michael

[mmo]

Searching for a solution I sstumbled over "Diagram Filters". Can one use these to remove those container prefixes? or can one use these only to filter entire elements?