t A4
>> CHAR 02/077
>> B-1049 Brussels/Belgium
>> +32 2 298 86 27
>> jorge.martin-cue...@ext.ec.europa.eu
>>
>> -----Original Message-----
>> From: Florian Müller [mailto:f...@apache.org]
>> Sent: Friday, August 23, 2013 5:45 PM
>> To: dev@ch
o: dev@chemistry.apache.org
Cc: MARTIN CUERVO Jorge (TRADE-EXT)
Subject: Re: CMIS 1.0 server is expecting CMIS 1.1 object type
feature
Hi Jorge,
Some layers above the converter we know which CMIS version is used.
For
the AtomPub binding we actually hand down that information to the
converter. Th
: dev@chemistry.apache.org
> Cc: MARTIN CUERVO Jorge (TRADE-EXT)
> Subject: Re: CMIS 1.0 server is expecting CMIS 1.1 object type feature
>
> Hi Jorge,
>
> Some layers above the converter we know which CMIS version is used. For
> the AtomPub binding we actually hand down that informa
rg
Cc: MARTIN CUERVO Jorge (TRADE-EXT)
Subject: Re: CMIS 1.0 server is expecting CMIS 1.1 object type feature
Hi Jorge,
Some layers above the converter we know which CMIS version is used. For
the AtomPub binding we actually hand down that information to the
converter. The AtomPub converter
Hi Jorge,
Some layers above the converter we know which CMIS version is used. For
the AtomPub binding we actually hand down that information to the
converter. The AtomPub converter skips CMIS 1.1 structures or warns the
developer if CMIS 1.1 details are provided in a CMIS 1.0 context. But
tha
Hello all,
We are working on a CMIS repository server and we have been using chemistry
0.8.0 for some time.
Recently we have upgraded to the latest version 0.10.0 and we have found some
unexpected behaviour.
Our goal is to comply with CMIS 1.0, so what I have made is to throw an
exception in t
