SOLVED: protege-dev Digest, Vol 1, Issue 8

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

SOLVED: protege-dev Digest, Vol 1, Issue 8

clemens utschig
Solved - believe it or not, a System.in.read() caused that mess .. what do I love swing / awt for there genius thread magic.

Btw, its very simple what I am trying to do - using a project within the protege app :-) (and I have not found a simple sample that would show this.)


thanks for all the help ...


On Tue, Feb 18, 2014 at 10:29 AM, clemens utschig <[hidden email]> wrote:
Reproduces completely standalone :-) . with the provided protege example
 
        Project p = new Project
            ("C:\\Program Files\\Protege_3.4.4\\examples\\newspaper\\newspaper.pprj", new ArrayList());
       
        Application.realmain(new String[] {});
        ProjectManager.getProjectManager().setExitVMOnApplicationExit(false);
        ProjectManager.getProjectManager().setCurrentProject(p, false, false);

opening an instance and attempting to change a value in there (key in some data ... )

This is a serious bug.


On Tue, Feb 18, 2014 at 10:14 AM, clemens utschig <[hidden email]> wrote:

So next steps - we are getting there - no more changes to the ontology, and still deadlocking...


        Application.main(new String[] {});
        ProjectManager.getProjectManager().setExitVMOnApplicationExit(false);
        ProjectManager.getProjectManager().setCurrentProject(p1.getProject(), false, false);

System.in.read();

I can assure you that I don't change anything on the KB directly now ... the moment I start changing an instance (click on an instance field and try to key in some information) the protege app (instance details) its (dead)locked.





_______________________________________________
protege-dev mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-dev