Simon, in terms of "radical surgery on namespaces and types", I think you will find the refactoring tools in Composer to be both comprehensive and accurate. Specifically, see Help > How to? > Refactor ontologies. Some of these may take a bit of getting used to, but any learning curve is easily recouped through making accurate changes. Making changes to source with non-RDF editors is specifically not recommended. This is experience talking, not vendor- speak. Knowing a bit of SPARQL to do some refactoring is also an invaluable tool.
In terms of the locking issue with Eclipse, In your workspace you will find a folder named .metadata. There is a .lock file that you can delete before starting Composer. This may remove the lock without needing to re-start your machine (I can't reproduce a lock issue at the moment - it is pretty rare). There are also -- Scott On Jan 19, 8:24 am, Bob DuCharme <[email protected]> wrote: > Simon, > > The crash and lock could be caused by any number of factors, but if you > really need to edit the RDF outside of TopBraid, I'd recommend : > > 1. After editing, check its syntax with some utility like jena rdfcat > (http://incubator.apache.org/jena/documentation/javadoc/jena/jena/rdfc...) > before loading it into TopBraid again to make sure that it's legal RDF, then > > 2. In TopBraid Composer, tell Eclipse to refresh its cache of the files in > that file's directory by selecting the containing folder in the Navigator > view and pressing F5. > > Bob > > > > > > > > On Thu, Jan 19, 2012 at 6:26 AM, Simon Cox <[email protected]> wrote: > > From time to time I manage to make TopBraid crash. I'm pretty sure its > > because I edit RDF in a text editor, sometimes doing some radical > > surgery on namespaces and types, in parallel with closing and opening > > it in TopBraid, so am not about to blame TopBraid for the instability. > > The crash message is > > > "IDE Exception Handler has encountered a problem. An internal > > error has occurred" > > > The problem is that I can't restart TB after such a crash. I find and > > kill one zombie TopBraid process. But then when I restart the > > workspace is locked. The only way I can get going again is to reboot > > my machine. > > > Is there an easier way to clean up after a crash without rebooting. > > > Sorry folks - I'm not much of a geek as I run on WinXP. > > > Simon > > > -- > > 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 -- 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
