Temporary file created by weaver visible to outside

[Matthias Schoettle]

The temporary file the weaver creates is deleted, however, when the user tries to save the resulting woven aspect, the name and location appears.

It seems that the resulting aspect still has the resource set. Therefore, we need to make sure that the resource is unloaded as well.

[Matthias Schoettle]

Resolved issue #146: Resource is unloaded in order for the temporary aspect to loose that reference. The temporary file is then not exposed to the user and it looks like when a new aspect is created.

An alternative would be to copy the woven aspect and use that one as the return.

→ <<cset e08e3de39056>>

[Matthias Schoettle]

References issue #146: Unloading the resource lead to an incorrect result when saving the woven aspect later. Therefore, a copy of the temporary aspect is created, which removes the link to the temporary resource.

→ <<cset 664d95394c5a>>