Mailing-List: contact dev-help@chemistry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@chemistry.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
To: <dev@chemistry.apache.org>
Subject: Re: Set content stream without checkout results in minor version
MIME-Version: 1.0
Content-Type: text/plain;
 charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Mon, 18 Jun 2012 16:09:29 +0200
From: =?UTF-8?Q?Florian_M=C3=BCller?= <fmui@apache.org>
Cc: <m.swerts@aca-it.be>
In-Reply-To: 
 <CAEkHLFM==S+dyFHdJeCHMaG1DcOH0xKbx=SshyX8NnCApcAvQg@mail.gmail.com>
References: 
 <CAEkHLFM==S+dyFHdJeCHMaG1DcOH0xKbx=SshyX8NnCApcAvQg@mail.gmail.com>
Message-ID: 
 <3f7ce97dc724893c7e725fc7514cb43d-EhVcXl9JQQFXRwQFDQkEXR0wfgZLV15fQUBFBEFYXS9aBFgIVQkjAVVfDwkJFE8AXVpYSlJXWAgwXnUFVVVfV1pHTA==-webmailer2@server03.webmailer.hosteurope.de>
User-Agent: Host Europe Webmailer/2.0

 Hi Mano,

 This behavior is repository specific. The CMIS interface does not 
 provide any option to control this.


 Cheers,

 Florian


> Hi all,
>
> We have a batch job that inserts or updates batch content in our 
> repository
> using CMIS. It seems to us that updating content would probably be 
> faster
> when done directly instead of using the checkout-checkin method.
> The only problem with this method is that it results in a minor 
> version
> increase instead of a major version. I do not see any option for
> instructing the repository to create a major version on content 
> update when
> not using checkout-checkin.
>
> Is there any other way to enforce the major version bump?
>
> Thanks in advance.
>
> Mano Swerts