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-discussion] WARNING: Errors at storing slot Slot

Tania Tudorache tudorache at stanford.edu
Tue Feb 5 12:27:01 PST 2008


This looks like the value of the ".ESCORT" slot was expected to be a 
String (because it has value type String) but it is actually an Integer.

So, you could inspect in the ontology the value of ".ESCORT" for the 
instance with the (very!) long name and fix it. I am not sure how this 
could have happened. Do you use a custom slot widget? If yes, then the 
slot widget added as value an Integer rather than a String object.

If not, can you please describe what steps led to this behavior?

Thanks,
Tania


protege at ontospace.net wrote:
> Hello Protege team, 
>
> What is the meaning of this:
>
>
> WARNING: Errors at storing slot Slot(.ESCORT) at instance SimpleInstance(new patient-_1/@INTAKE/INTAKEID=50109, at TEAM/TEAMID=3, at BRANCH/BRANCHID=21, at COMPANY/COMPANYID=6, at EMPLOYEE_KEY/EMPLOYEEID=13282, at CASETYPEREF/CASETYPEID=417, at PATIENT/PATIENTID=61286, at PROFILELOVITEM/LOVITEMID=92, at ITEMCATEGORY/CATEGORYID=0, at INSTITUTION/INSTITUTIONID=583,INSTTABLETID=0 of [Cls(new patient-_1, FrameID(6:14121 1))]) -- java.lang.ClassCastException: java.lang.Integer
> 	at edu.stanford.smi.protege.storage.clips.InstanceStorer.internalToExternalStrings(InstanceStorer.java:139)
> 	at edu.stanford.smi.protege.storage.clips.InstanceStorer.storeSlotValue(InstanceStorer.java:286)
> 	at edu.stanford.smi.protege.storage.clips.InstanceStorer.storeSlotValues(InstanceStorer.java:313)
> 	at edu.stanford.smi.protege.storage.clips.InstanceStorer.storeInstance(InstanceStorer.java:230)
> 	at edu.stanford.smi.protege.storage.clips.InstanceStorer.storeInstances(InstanceStorer.java:261)
> 	at edu.stanford.smi.protege.storage.clips.ClipsKnowledgeBaseFactory.saveKnowledgeBase(ClipsKnowledgeBaseFactory.java:142)
> 	at edu.stanford.smi.protege.storage.clips.ClipsKnowledgeBaseFactory.saveKnowledgeBase(ClipsKnowledgeBaseFactory.java:154)
> 	at edu.stanford.smi.protege.storage.clips.ClipsKnowledgeBaseFactory.saveKnowledgeBase(ClipsKnowledgeBaseFactory.java:131)
> 	at edu.stanford.smi.protege.model.Project.saveDomainKB(Project.java:1742)
> 	at edu.stanford.smi.protege.model.Project.save(Project.java:1683)
> 	at edu.stanford.smi.protege.ui.ProjectManager.save(ProjectManager.java:755)
> 	at edu.stanford.smi.protege.ui.ProjectManager.saveProjectRequest(ProjectManager.java:808)
> 	at edu.stanford.smi.protege.ui.ProjectManager.confirmSave(ProjectManager.java:303)
> 	at edu.stanford.smi.protege.ui.ProjectManager.closeProjectRequest(ProjectManager.java:239)
> 	at edu.stanford.smi.protege.ui.ProjectManager.exitApplicationRequest(ProjectManager.java:381)
> 	at edu.stanford.smi.protege.Application$1.windowClosing(Application.java:93)
> 	at java.awt.AWTEventMulticaster.windowClosing(Unknown Source)
> 	at java.awt.Window.processWindowEvent(Unknown Source)
> 	at javax.swing.JFrame.processWindowEvent(Unknown Source)
> 	at java.awt.Window.processEvent(Unknown Source)
> 	at java.awt.Component.dispatchEventImpl(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.pumpOneEventForHierarchy(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)
>
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 
>
>   




More information about the protege-discussion mailing list