Comments on the changed behaviour for association targets class lookup

This commit is contained in:
Andrea Aime 2005-12-31 17:31:35 +00:00
parent 4ad5a8ff64
commit 625a6d3cb3
2 changed files with 7 additions and 0 deletions

View File

@ -51,6 +51,8 @@ to enclose stereotype names.
These will be automatically enclosed in guillemots.
Note that a relationship's target class is not implicitly
defined; it should also be specified using the Java class syntax.
The target can be specified by simple name, java class lookup rules
(imports and visibility) will be used to determine the actual class.
The following is an example of a relationship
specification and the resulting UML diagram:
<table>

View File

@ -7,6 +7,11 @@
<ul>
<li> Correct the handling of qualified class names following
the extends keyword (Arnaud Rogues).</li>
<li> Standard class lookup for association targets. The target can be
specified by name without the need to include the full package
information, imports and standard visibility rules will be applied
to determine the actual class
</li>
<li> A <em>views</em> feature provides the ability to specify package-based
option overrides in UMLOptions like classes,
and to generate multiple diagrams out of a code base in a single pass.