Description Christian Waniek 2010-07-19 07:19:29 EDT

Build Identifier: 

If you create a navigable association between two classes, the source class holds an ownedAttribute, pointing to the target class of the association. So far, everything is correct (in my opinion).
But when you delete the association, this ownedAttribute remains in its class. From an EMF-view this is correct, because the metaclass Association has no controll over features of the metaclass Class. But from an UML-view this is a bug.

As far as I see the source for this bug is, that an association is created via the Type.createAssociation(...). This calls some custom code which writes the ownedAttribute to the source class. But theres is no equivalent to delete an association, which checks whether one of the associations memeberEnds has an ownedAttribute which refers to this association.

I found this bug while fixing some bugs for the UML2 Tools.

Reproducible: Always

Steps to Reproduce:
To reproduce, use the following code-snippet and look at the created file. After this uncomment the commented line, execute again and look at the created uml-file. You'll see, that 'class ONE' still holds an ownedAttribute, which should have been deleted by deleting the association.

public static void main(String[] args) {
		// TODO Auto-generated method stub
		Package p = UMLFactory.eINSTANCE.createPackage();
		p.setName("myPackage");

		Class c1 = UMLFactory.eINSTANCE.createClass();
		c1.setPackage(p);
		c1.setName("class ONE");
		Class c2 = UMLFactory.eINSTANCE.createClass();
		c2.setPackage(p);
		c2.setName("class TWO");

		Association a = c1.createAssociation(true,
				AggregationKind.NONE_LITERAL, "end1", 0, 1, c1, false,
				AggregationKind.NONE_LITERAL, "end2", 0, 1);
		a.setPackage(p);

		// a.destroy();

		ResourceSet resourceSet = new ResourceSetImpl();

		resourceSet.getResourceFactoryRegistry().getExtensionToFactoryMap()
				.put("uml", new XMLResourceFactoryImpl());

		URI fileURI = URI
				.createFileURI(new File("myUML.uml").getAbsolutePath());
		Resource resource = resourceSet.createResource(fileURI);

		resource.getContents().add(p);

		try {
			resource.save(null);
		} catch (IOException e) {
			System.out.println("IOException while saving model-instance.");
			e.printStackTrace();
		}
	}