Weaving Workflow produces exception due to weaver problem

[Matthias Schoettle]

Steps to reproduce:

• Open Workflow
• Weave the first ZeroToMany
• Weave the second ZeroToMany

Result:

java.lang.NullPointerException
    at org.mt4j.components.MTComponent.getLocalVecToParentRelativeSpace(MTComponent.java:1003)
    at ca.mcgill.ram.ui.views.RelationshipView.updateLines(RelationshipView.java:580)
    at ca.mcgill.ram.ui.views.StructuralDiagramView.addAssociationView(StructuralDiagramView.java:223)
    at ca.mcgill.ram.ui.views.StructuralDiagramView.<init>(StructuralDiagramView.java:186)
    at ca.mcgill.ram.ui.scenes.DisplayAspectScene.buildViews(DisplayAspectScene.java:325)
    at ca.mcgill.ram.ui.scenes.DisplayAspectScene.<init>(DisplayAspectScene.java:133)
    at ca.mcgill.ram.RamApp.getExistingOrCreateAspectScene(RamApp.java:315)
    at ca.mcgill.ram.RamApp$2.run(RamApp.java:388)
    at org.mt4j.AbstractMTApplication.runApplication(AbstractMTApplication.java:359)
    at org.mt4j.AbstractMTApplication.draw(AbstractMTApplication.java:272)
    at processing.core.PApplet.handleDraw(PApplet.java:1603)
    at processing.core.PApplet.run(PApplet.java:1502)
    at java.lang.Thread.run(Thread.java:680)

It works in TouchRAM 2.1.0 and is broken in TouchRAM 2.2.1, so it probably was introduced when dealing with issues for the SlotMachine assignment.

There is an association from Set to WorkflowNode (a Set of WorkflowNode already exists at that point), and the Set class referenced in the AssocationEnd (its container) is not contained by anything.

[Wisam Al Abed]

Resolved #105: Fixed issue temporarly with zeroToMany being woven into workflow twice and having the dangling set class.

→ <<cset 73a3397453b9>>

[Wisam Al Abed]

Resolved #105: Improved the code by creating a temporary local hashmap that keeps track of a subset of the mappings creating in mappingInfo and ensures those are added to weavingInformation

→ <<cset 7f29550662ac>>

[Matthias Schoettle]

Problem was due to changes from commit 603ba69.