chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Brackx <>
Subject Re: Proposed change TypeManager
Date Mon, 26 Aug 2013 10:02:46 GMT

I was about to suggest the opposite: to drop the unused methods from that
It feels wrong to have to implement this complete interface to use the
query support. Only recently did I discover that I had some unused code
because of this.
Maybe we can have 2 interfaces. One minimal to use with the query support
and one full with the currently unused methods and your new proposed

In general this interface is not that useful to me, as it is for one
repository only. An extra repositoryId parameter for all methods would
improve that.


On Fri, Aug 23, 2013 at 7:49 AM, Huebel, Jens <> wrote:

> Hi all,
> in the server-support package we have an interface TypeManager that is
> used by the query parser to get access to the CMIS type definitions. With
> CMIS 1.1 we have added type mutability. The InMemory server therefore has
> added an interface extension like this:
> public interface TypeManagerCreatable extends TypeManager {
>     void addTypeDefinition(TypeDefinition typeDefinition, boolean
> addInheritedProperties);
>     void updateTypeDefinition(TypeDefinition typeDefinition);
>     void deleteTypeDefinition(String typeId);
> }
> I guess that many server implementations do something similar and wonder
> if we should add these methods to the TypeManager interface. Serves not
> implementing type mutability simply can throw an exception. Of course these
> methods are not needed by the query parser. But from my perspective
> TypeManager is a more generic interface and it seems simpler and cleaner to
> add type mutability there.
> Any thoughts? If no one objects I will add these methods with the 1.0
> release.
> Jens

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message