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

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

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

clemens utschig

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
Reply | Threaded
Open this post in threaded view
|

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

clemens utschig
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
Reply | Threaded
Open this post in threaded view
|

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

Timothy Redmond

I did not replicate this.  I haven't done any Protege 3 hacking in a while but I just setup a development environment and tried your example.  A stack trace would tell us what happened.

-Timothy

On 02/18/2014 01:29 AM, clemens utschig 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


_______________________________________________
protege-dev mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-dev
Reply | Threaded
Open this post in threaded view
|

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

Tania Tudorache
I did not reproduce the bug either.

The methods you are calling are really internal, and an application is not supposed to call. These methods are part of the initialization, and suppose a certain order, etc.

What are you trying to do? I am sure there are better and more "official" ways of doing it.

Maybe this link will help:
http://protegewiki.stanford.edu/wiki/UseProtegeFormsInApplications

Tania


On 02/18/2014 06:14 AM, Timothy Redmond wrote:

I did not replicate this.  I haven't done any Protege 3 hacking in a while but I just setup a development environment and tried your example.  A stack trace would tell us what happened.

-Timothy

On 02/18/2014 01:29 AM, clemens utschig 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



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


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