When I first tried spin:constructors last year, I noticed (in TBCME) that graph created by a cascade of spin constructors deleted when you deleted the root (initiating) object in a spin constructor cascade. I thought this was a great feature, and thought I would find some documentation on it that explained its semantics and would like to use it, but have not found docs yet and have not seen any discussion on it on the news group. I spent the afternoon playing around with it to confirm that it still worked and to re-acquaint myself with it. I also made a concerted effort to find documentation and came up short.
I have questions: Is it an intended feature? How does it work? How does TopBraid keep track of dependencies? (I noticed a TBC file got created for my model, but did not check the contents) Under what conditions is it safe to use? What happens if subsequent changes are made to the structure that was created by the constructor? How do you use it in Ensemble/Live? I tested a SM script that replicates the behavior seen from Composer. I found that by calling TopSpin on spin:constructor after deleting the root object in a perform update, TopSpin returned the set of triples that were created by the original constructor execution, so I was able to route them into a Perform Update that delete them. My test constructor is on a Project class that creates a default set of child tasks and links them into a precedence network. Deleting the project instance takes out everything Arthur -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en
