Re: association between classes in diferent packages

I noticed this problem as well when trying to create a diagram that showed
an API/SPI implementation (similar to what you might see if you were
diagramming JDBC driver implementations, or XML parser implementations).

What's more, it wouldn't allow you to place the implementing class in the
proper package.  For example if you were implementing your own JDBC driver (
com.mydriver.Driver) which implemented java.sql.Driver, it won't allow you
to put your driver into a separate package. The package combo box wouldn't
allow you to select or enter the proper package name.  It always forced the
package to be the top-level project package.

Hope this helps,

Mark

On 7/13/07, Tom Morris <[email protected]> wrote:
>
> OK, the screen capture makes it clearer what you are trying to do.  I
> didn't
> understand that you were making an association between classes which were
> in
> two different packages.  That wasn't the case I tested.
>
> The association is being put in the closest common namespace (package in
> this case).  I thought that the rules would be less strict for
> non-navigable
> association ends, but I don't see the behavior changing in this case.  I'd
> need to double check the well formedness rules in the UML 1.4 spec, but I
> suspect they are what's driving this behavior.  Or it could just be a
> misintepretation of those rules...
>
> Why don't you file a bug report so that it doesn't fall through the
> cracks?
> I'm not 100% sure what the correct behavior is off the top of my head and
> don't have time to check right now.
>
> Tom
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>