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

Tania Tudorache tudorache at
Tue Jul 27 17:53:51 PDT 2010

Brice, the solution depends on your scenario. If you modify the imported 
ontology using the server through the importing ontology (e.g. delete an 
imported class), then all your clients will see that change.

However, if you modify the imported ontology outside of the Protege 
server, then there is no way for the server to know that the underlying 
DB has changed.

Also, if you have two different remote ontologies on the server (one for 
the importing, and for the imported), they will not be aware of each other.

There is some experimental code that allows you to set the active 
ontology in client-server mode. Then, you could load the importing 
ontology and set as the active ontology the imported ontology. All 
changes that you make will go into the imported ontology, and the other 
clients that have loaded the importing ontology, will see the change. 
But, this is still experimental code..


On 07/27/2010 01:12 PM, Csongor Nyulas wrote:
> Oh, sorry. I realized that using Protege Client-Server would not solve 
> the problem of changing the importED ontology.
> Because the loading of the imported ontology happens during the server 
> start-up, if you change one of the imported ontology you will need to 
> reload the project (see [1]). Or at least I am not aware of any other 
> solution.
> Csongor
> [1] 
> On 7/27/2010 10:16 AM, Brice Sommacal wrote:
>> Thanks, but I already use it...
>> I did not mention that I use global and specific repositories. Does 
>> it matter?
>> Brice
> _______________________________________________
> protege-owl mailing list
> protege-owl at
> Instructions for unsubscribing: 

More information about the protege-owl mailing list