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
Fri Jul 30 01:00:17 PDT 2010


Hi Tania,

Thanks for the explanation. I get it now :-)

Brice

2010/7/29 Tania Tudorache <tudorache at stanford.edu>

>  It seems like you are trying to add an import from a client using the
> Metadata Tab. This feature is not supported from a client (same reason that
> the set active ontology does not work in client-server mode).
>
> If you have a running Protege server, you can shutdown the project using
> the Server Admin Console, open the project in Protege standalone on the
> server, perform the import, and then restart the project using the Server
> Admin Console. When the users log back in, the import will be visible.
>
> Tania
>
>
>
> On 07/29/2010 09:19 AM, Brice Sommacal wrote:
>
> Hello,
>
>  I tryed to import an ontology from a database repository (mysql) and it
> returns the following error. Firstly, I thought it was due to the "set
> active ontology" button... but it seems not.
>
>  Importing
> http://seamless.pco-innovation.com/energy/common/subject/seam/dsea/bz from
> location: Table bzcommon of the da
> abase jdbc:mysql://localhost/protege
> java.lang.UnsupportedOperationException
>         at
> edu.stanford.smi.protegex.owl.server.triplestore.ClientTripleStoreModel.createActiveImportedTripleStore(Unkn
> wn Source)
>         at
> edu.stanford.smi.protegex.owl.repository.impl.DatabaseRepository.loadImportedAssertions(Unknown
> Source)
>         at
> edu.stanford.smi.protegex.owl.model.impl.AbstractOWLModel.loadImportedAssertions(Unknown
> Source)
>         at
> edu.stanford.smi.protegex.owl.model.util.ImportHelper.importOntologies(Unknown
> Source)
>         at
> edu.stanford.smi.protegex.owl.model.util.ImportHelper.importOntologies(Unknown
> Source)
>         at
> edu.stanford.smi.protegex.owl.ui.importstree.ImportsTreePanel.addImport(Unknown
> Source)
>         at
> edu.stanford.smi.protegex.owl.ui.importstree.ImportsTreePanel.access$100(Unknown
> Source)
>         at
> edu.stanford.smi.protegex.owl.ui.importstree.ImportsTreePanel$2.actionPerformed(Unknown
> Source)
>         at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
>         at javax.swing.AbstractButton$Handler.actionPerformed(Unknown
> Source)
>         at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown
> Source)
>         at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
>         at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown
> Source)
>         at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
>         at java.awt.Component.processMouseEvent(Unknown Source)
>         at javax.swing.JComponent.processMouseEvent(Unknown Source)
>         at java.awt.Component.processEvent(Unknown Source)
>         at java.awt.Container.processEvent(Unknown Source)
>         at java.awt.Component.dispatchEventImpl(Unknown Source)
>         at java.awt.Container.dispatchEventImpl(Unknown Source)
>         at java.awt.Component.dispatchEvent(Unknown Source)
>         at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown
> Source)
>         at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
>         at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
>         at java.awt.Container.dispatchEventImpl(Unknown Source)
>         at java.awt.Window.dispatchEventImpl(Unknown Source)
>         at java.awt.Component.dispatchEvent(Unknown Source)
>         at java.awt.EventQueue.dispatchEvent(Unknown Source)
>         at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown
> Source)
>         at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
>         at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown
> Source)
>         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
>         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
>         at java.awt.EventDispatchThread.run(Unknown Source)
>
>
>  Brice
> 2010/7/29 Brice Sommacal <brice.sommacal at gmail.com>
>
>> Hi Tania,
>>
>>  Thanks in advance, I will be glad to try it.
>>
>>
>>  Brice
>> 2010/7/28 Tania Tudorache <tudorache at stanford.edu>
>>
>>>  Hi Brice,
>>>
>>> You need to set a property in order to use the set active ontology in
>>> client-server. We have deliberately made this feature configurable (default
>>> it is disabled) because the feature is experimental. To enable it, you need
>>> to add a property in the protege.property file. I will look it up, and send
>>> it to you, if you want to try it.
>>>
>>> Tania
>>>
>>>
>>>
>>> On 07/28/2010 01:17 AM, Brice Sommacal wrote:
>>>
>>> Hello Tania,
>>>
>>>  I made the following try and it's mainly working, but thrown me an
>>> error (see below).
>>>
>>>      1- Open the imported ontology (named A)
>>>     2- Add a new Class in A
>>>     3- Open the importing ontology (named B)
>>>
>>>  From there, the new Class is not viewable.
>>> In metadata tab, select the imported ontology, and click on "Set active
>>> ontology"
>>> => The new class is displayed.
>>>
>>>  In the inverse way, I tryed to delete the class.
>>>
>>>      1- Open the imported ontology (named A)
>>>     2- Delete class in A
>>>     3- Open the importing ontology (named B)
>>>
>>>  The class A still there. So, I clicked on "Set active otology" like
>>> preceding, but the class A still be there.
>>> Then, I removed the imported ontology, and imported it again. But it
>>> thrown me an error.
>>> I close the projet, and re-open it.
>>>
>>>  From now, In the metadata tab, the imported ontology does not appear
>>> anymore. The class A was still being displayed, but its prefix was not set.
>>> (eg. instead of bz:A, I saw http://www.ontologie.com/class#A).
>>>
>>>  Then I clicked on "set active ontology" on the main one. (eg. the
>>> importing ontology) and in class and property tabs, the display is correct.
>>> (with namespaces, and without class A)
>>>
>>>  So far, it came back in a normal display.
>>>
>>>  But, in the metadata tab, the imported ontology does not appear. Even
>>> trying to re-import the ontology, I obtain this error:
>>>
>>>  java.lang.UnsupportedOperationException
>>>         at
>>> edu.stanford.smi.protegex.owl.server.triplestore.ClientTripleStoreModel.createActiveImportedTripleStore(Unkno
>>> wn Source)
>>>         at
>>> edu.stanford.smi.protegex.owl.repository.impl.DatabaseRepository.loadImportedAssertions(Unknown
>>> Source)
>>>         at
>>> edu.stanford.smi.protegex.owl.model.impl.AbstractOWLModel.loadImportedAssertions(Unknown
>>> Source)
>>>         at
>>> edu.stanford.smi.protegex.owl.model.util.ImportHelper.importOntologies(Unknown
>>> Source)
>>>         at
>>> edu.stanford.smi.protegex.owl.model.util.ImportHelper.importOntologies(Unknown
>>> Source)
>>>         at
>>> edu.stanford.smi.protegex.owl.ui.importstree.ImportsTreePanel.addImport(Unknown
>>> Source)
>>>         at
>>> edu.stanford.smi.protegex.owl.ui.importstree.ImportsTreePanel.access$100(Unknown
>>> Source)
>>>         at
>>> edu.stanford.smi.protegex.owl.ui.importstree.ImportsTreePanel$2.actionPerformed(Unknown
>>> Source)
>>>         at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
>>>         at javax.swing.AbstractButton$Handler.actionPerformed(Unknown
>>> Source)
>>>         at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown
>>> Source)
>>>         at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
>>>         at
>>> javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
>>>         at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
>>>         at java.awt.Component.processMouseEvent(Unknown Source)
>>>         at javax.swing.JComponent.processMouseEvent(Unknown Source)
>>>         at java.awt.Component.processEvent(Unknown Source)
>>>         at java.awt.Container.processEvent(Unknown Source)
>>>         at java.awt.Component.dispatchEventImpl(Unknown Source)
>>>         at java.awt.Container.dispatchEventImpl(Unknown Source)
>>>         at java.awt.Component.dispatchEvent(Unknown Source)
>>>         at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown
>>> Source)
>>>         at java.awt.LightweightDispatcher.processMouseEvent(Unknown
>>> Source)
>>>         at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
>>>         at java.awt.Container.dispatchEventImpl(Unknown Source)
>>>         at java.awt.Window.dispatchEventImpl(Unknown Source)
>>>         at java.awt.Component.dispatchEvent(Unknown Source)
>>>         at java.awt.EventQueue.dispatchEvent(Unknown Source)
>>>         at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown
>>> Source)
>>>         at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown
>>> Source)
>>>         at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown
>>> Source)
>>>         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
>>>         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
>>>         at java.awt.EventDispatchThread.run(Unknown Source)
>>>
>>>
>>>  BR,
>>>
>>>
>>>  Brice
>>>
>>>  2010/7/28 Tania Tudorache <tudorache at stanford.edu>
>>>
>>>> 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..
>>>>
>>>> Cheers,
>>>> Tania
>>>>
>>>>
>>>>
>>>> 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]
>>>>> http://protegewiki.stanford.edu/wiki/Protege_Client_Server_Tutorial_Administration
>>>>>
>>>>> 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 lists.stanford.edu
>>>>> https://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
>>>>
>>>
>>>
>>> _______________________________________________
>>> protege-owl mailing listprotege-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
>>>
>>>
>>
>
> _______________________________________________
> protege-owl mailing listprotege-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/20100730/7b522b56/attachment.html>


More information about the protege-owl mailing list