Hi Thomas/Tom

I assume one example of what Tom is discussing is the following.

Place two packages on a diagram, package1 and package2

Add two classes, both called Date placing one in package1 and one in package2

Create another class in package 1 and create a new attribute by double
clicking the attribute box, enter "+newAttr : Date" and press enter.

[There is now a bug, you must unselect and then reselect the attribute]

You see here that the search to find the Date class was quite sensibly
in the same package as the class referring to Test.

But what to do if the class is not found there?

Do we search the entire model and if so how do we iterate through or
do we create a new class/Interface in the same package?

Try the above again but with a Date class only in package2. The code
currently matches with that. I would think it far more sensible when
using the Java profile to match with the Date class there.

So for this example I would say current package for non-private
classifiers and then iterate through profile models looking for public
classifiers.

After that I'm not sure what is best. If we want to iterate through
the entire model then I think child packages first, then go up one and
do child packages repeatedly until something is found.

But do we give up at some time before then and just create a class or
interface in the local package?

It would nice to have a ctrl-space feature to pattern match in the
attribute editor, also to be able to specify the full package name for
Date to explicitly state the class required.

> It's my belief that namespaces in UML work exactly like they do in
> most programming languages and that you can "see" out/up towards
> enclosing namespaces, but you can not, without an import, see into
> peer or child namespaces.
Well it's not like this in Java, you can't see any other namespace
without an import. So I'm really unsure. If there is any logic along
these lines I'd have thought it more likely that a namespace would
know it's contained namespaces rather than the other way round. Very
unsure though.

Bob.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to