You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-dev@jakarta.apache.org by Michael Smith <ms...@xn.com.au> on 2002/09/18 07:25:34 UTC

auto-versioning bug

Hi,

I've run into a problem with auto-versioning in the current slide
server.
I have the server configured with:
   <parameter name="auto-version">checkout-unlocked-checkin</parameter>
   <parameter name="auto-version-control">true</parameter>

If I create (doing a PUT) a new resource, it gets put under version
control.
If, however, I do a LOCK, _then_ a PUT, followed by an UNLOCK, the new
resource is not version-controlled unless I do an explicit
VERSION-CONTROL request afterwards.

Is this what the spec mandates? (I can't find anything that says this,
but it's pretty densely written and easy to miss things), or is this a
bug?

Michael

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: auto-versioning bug

Posted by Ingo Brunberg <ib...@fiz-chemie.de>.
Hi Mike,

I'm sorry, I gave you the wrong answer. I was so used to the bug
myself, that I thought this behviour was in conformance with the spec.

> Ingo Brunberg wrote:
> > 
> > > Hi,
> > >
> > > I've run into a problem with auto-versioning in the current slide
> > > server.
> > > I have the server configured with:
> > >    <parameter name="auto-version">checkout-unlocked-checkin</parameter>
> > >    <parameter name="auto-version-control">true</parameter>
> > >
> > > If I create (doing a PUT) a new resource, it gets put under version
> > > control.
> > > If, however, I do a LOCK, _then_ a PUT, followed by an UNLOCK, the new
> > > resource is not version-controlled unless I do an explicit
> > > VERSION-CONTROL request afterwards.
> > >
> > > Is this what the spec mandates?
> > 
> > Yes, it is. So it's not a bug.
> 
> Can you be more specific? Where does it say this, and why? All I can
> find on the subject of auto-version-control in the spec is the bit in
> 2.2.1 where it says that servers are allowed to do it. 
> 
> The behaviour seems counterintuitive, apart from anything else.
> 
> Mike


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: auto-versioning bug

Posted by Michael Smith <ms...@xn.com.au>.
Ingo Brunberg wrote:
> 
> > Hi,
> >
> > I've run into a problem with auto-versioning in the current slide
> > server.
> > I have the server configured with:
> >    <parameter name="auto-version">checkout-unlocked-checkin</parameter>
> >    <parameter name="auto-version-control">true</parameter>
> >
> > If I create (doing a PUT) a new resource, it gets put under version
> > control.
> > If, however, I do a LOCK, _then_ a PUT, followed by an UNLOCK, the new
> > resource is not version-controlled unless I do an explicit
> > VERSION-CONTROL request afterwards.
> >
> > Is this what the spec mandates?
> 
> Yes, it is. So it's not a bug.

Can you be more specific? Where does it say this, and why? All I can
find on the subject of auto-version-control in the spec is the bit in
2.2.1 where it says that servers are allowed to do it. 

The behaviour seems counterintuitive, apart from anything else.

Mike

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: auto-versioning bug

Posted by Ingo Brunberg <ib...@fiz-chemie.de>.
> Hi,
> 
> I've run into a problem with auto-versioning in the current slide
> server.
> I have the server configured with:
>    <parameter name="auto-version">checkout-unlocked-checkin</parameter>
>    <parameter name="auto-version-control">true</parameter>
> 
> If I create (doing a PUT) a new resource, it gets put under version
> control.
> If, however, I do a LOCK, _then_ a PUT, followed by an UNLOCK, the new
> resource is not version-controlled unless I do an explicit
> VERSION-CONTROL request afterwards.
> 
> Is this what the spec mandates?

Yes, it is. So it's not a bug.

> (I can't find anything that says this,
> but it's pretty densely written and easy to miss things), or is this a
> bug?
> 
> Michael

Regards,
Ingo


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>