Search Mailing List Archives


Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[protege-dev] protege-dev Digest, Vol 1, Issue 8

Timothy Redmond tredmond at stanford.edu
Tue Feb 18 06:14:58 PST 2014


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 
> <clemens.utschig at gmail.com <mailto:clemens.utschig at gmail.com>> 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
> protege-dev at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.stanford.edu/pipermail/protege-dev/attachments/20140218/9d3dd3cc/attachment.html>


More information about the protege-dev mailing list