What steps will reproduce the problem?
1. Copy assotiation type in
What is the expected output? What do you see instead?
A new association that I can modify(change names,...) while others remain
It seems that the copy isn´t complete and part of it "is" the original
association. The problem dissapear when I delete the copy and do it again
as a new assotiation.
Please use labels and text to provide additional information.
Original issue reported on code.google.com by mjcolmen...@gmail.com on 23 Sep 2009 at 11:29
The text was updated successfully, but these errors were encountered:
I'm sorry, but I don't really understand this error report. What tool were you
using? When you say "copy association type", what action are you actually
performing, and where? If you can provide more detail we should be able to fix
Original comment by lar...@gmail.com on 25 Sep 2009 at 8:36
I´ll try to explain better. I'm using Ontopia 5.0.2 release.
In a topic map, I choose an assotiation that already has been created (attached
pantalla1). After that I get a copy by clicking the button "copy", at the right
of the screen, with "Create new Association type" on top (attached file
In this new association, I may modify name and roles, used by, ...etc, to made a
really new association. But it isn´nt new. It seem that a link remains between
old and new (the copy) assotiation.
Original comment by mjcolmen...@gmail.com on 13 Oct 2009 at 9:11
I tried this myself now, and while it seems like the fields on the association
itself, such as name, comment, and description can be edited just fine, I found
deleting the roles from the copied association type also deleted them from the
original. So there is definitely a bug here.
Original comment by lar...@gmail.com on 14 Oct 2009 at 9:53
The copy operation does not take into account that some of the characteristics
the association type (this applies to other types as well) are really meant to
used by only a single topic. A shallow copy of the association type's
characteristics does not really work in this situation. A deep copy is
we want to support copying of association types.
We have to options: 1) disable the Copy button 2) implement deep copying that
duplicates the associated characteristics (e.g. the referenced field-definition
Original comment by email@example.com on 14 Oct 2009 at 6:03
I'd be just as happy to disable the button, personally. I don't think copying
association types is a very useful thing to be doing in most cases. Just about
everything will have to be redefined for the new association type, anyway. In
cases, at least.
Original comment by lar...@gmail.com on 14 Oct 2009 at 6:11