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-owl] Protege server - Need to restart server to make the changes up

Brice Sommacal brice.sommacal at gmail.com
Tue Jul 27 10:16:43 PDT 2010


Thanks, but I already use it...

I did not mention that I use global and specific repositories. Does it
matter?


Brice

2010/7/27 Csongor Nyulas <csongor.nyulas at stanford.edu>

>  To solve this issue Protege Client-Server is your best option.
>
> Csongor
>
>
> On 7/27/2010 8:08 AM, Brice Sommacal wrote:
>
> Hello,
>
>  Let suppose that Ontology B is imported by Ontology A.
>
>  Working with Protege server (DB backend), if a change is made on ontology
> B; the server have to be restarted to see the changes in ontology A.
>
>  How to evitate this behavior?
>
>  Thanks for sharing your mind,
>
>  BR,
>
>
>  Brice
>
>
> _______________________________________________
> protege-owl mailing list
> protege-owl at lists.stanford.eduhttps://mailman.stanford.edu/mailman/listinfo/protege-owl
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
>
>
>
> _______________________________________________
> protege-owl mailing list
> protege-owl at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>
> Instructions for unsubscribing:
> http://protege.stanford.edu/doc/faq.html#01a.03
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.stanford.edu/pipermail/protege-owl/attachments/20100727/d0e1a32d/attachment.html>


More information about the protege-owl mailing list