cancel
Showing results for 
Search instead for 
Did you mean: 

CMIS Exception thrown changed from 5.8 to 5.9.2

rdifrango_
Champ in-the-making
Champ in-the-making

I recently upgraded from 5.8 to 5.9.2 and it seems as if the exception that is thrown when a search is performed by path, changed from CmisObjectNotFoundException to CmisRuntimeException, any particular reason for this as it makes it hard to differentiate between a not found and an error.

I would have expected a NOT Found in all cases.

Here’s the stack trace:

2014-03-05 11:45:59,174 [main] ERROR com.capitalone.tst.opentst.content.receiver.service.impl.ReceiverCacheContentServiceImpl - Error locating the interface org.apache.chemistry.opencmis.client.api.Document at /default-domain/workspaces/tst-refapp-consumer-app/IPCpitcher/help_ipcpitcher.xml
org.apache.chemistry.opencmis.commons.exceptions.CmisRuntimeException: org.nuxeo.ecm.core.api.ClientException: Failed to check existence of /default-domain/workspaces/tst-refapp-consumer-app/IPCpitcher/help_ipcpitcher.xml
	at org.apache.chemistry.opencmis.client.bindings.spi.atompub.AbstractAtomPubService.convertStatusCode(AbstractAtomPubService.java:452)
	at org.apache.chemistry.opencmis.client.bindings.spi.atompub.AbstractAtomPubService.read(AbstractAtomPubService.java:554)
	at org.apache.chemistry.opencmis.client.bindings.spi.atompub.AbstractAtomPubService.getObjectInternal(AbstractAtomPubService.java:778)
	at org.apache.chemistry.opencmis.client.bindings.spi.atompub.ObjectServiceImpl.getObjectByPath(ObjectServiceImpl.java:524)
2 REPLIES 2

rdifrango_
Champ in-the-making
Champ in-the-making

I figured it out, when I upgraded, I also changed the content type name [mis-spelled] and although I deleted everything from the UI it seems as if my content was still hanging around. Fortunately in my case, it was just development so I could blow away all this DB and start from scratch.

The question I had was, if in the future we need to change our custom types name, what is the process to do so?

If I understand your question correctly, you'd need to do an update in the database at the SQL level (column primarytype of the table hierarchy).