Andriy; The most effective way to design such processes is to use SPARQLMotion scripts. If you need to create a customizable end-user interface, TopBraid Ensemble is designed for building such applications.
-- Scott On Jun 8, 9:22 am, Andriy Sokolov <[email protected]> wrote: > Hello! > > By writing some Java-Code in TBC I want to make tests, if some new > Predicate-Object-pairs on a particular Subject would violate some spin > constraints on this Subject. For this purpose, I remember old pairs, > switch-off change engine (setIgnoreMode(true), i dont want that it > fires changes and writes it into undo/redo), replase old with new ones > (delete 4 + add 4 pairs), check the changed model with > SPINConstraints.check(), then replace new P-O-pairs again with the old > ones ( 4+4), and switch change engine on again. So I make 16(!) change > operations for 4 > properties just to test it. May be there is a way I can do this check > much more efficiently? Or, second possibility, how can I achieve TBC > dont rebuild its views on this checks? > > Thanks, > Andriy -- 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
