Hi Florent, I think a CmisObjectNotFoundException is more appropriate than a CmisInvalidArgumentException. The object, in this case the type, is not found. The client did not provide an invalid value like a wrong enum value or a value out of range.
In HTTP terms, it's rather a 404 than a 400. - Florian On 25/10/2011 07:23, Florent Guillaume wrote: > Hi, > > In my repository, o.a.c.o.client.api.Session.getTypeDefinition throws > a when you pass it an unknown type > (cmis:policy in my case). However the TCK > (AbstractSessionTest.hasPolicies in my case, but there are other > places) expects a CmisObjectNotFoundException. > > I think that should be a legit exception for this case, but I'm open > to arguments why not. If you think it's ok, I can change the TCK (and > document the exceptions on the interface). > > Florent >
