You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chemistry.apache.org by Michael Brackx <mi...@gmail.com> on 2013/03/13 10:05:47 UTC
tck - versionSeriesId
Hi,
On trunk the tck now checks that versionSeriesId's are different for
multiple new documents.
However, my understanding is that the versionSeriesId is repository
specific if the document is not versionable.
For example it could use "none" for all documents.
Should the check not be conditional on versionable attribute of the type?
Michael
Re: tck - versionSeriesId
Posted by Florian Müller <fm...@apache.org>.
There are probably a lot, but nothing specific comes to mind.
Check the TCK warnings. Several TCK checks have been added in reaction
to real world issues.
If you have come across something generic, let us know and we add a TCK
test.
- Florian
> Hi,
>
> Are there any other recommendations for servers for use with real
> world clients?
>
> Michael
>
> On Wed, Mar 13, 2013 at 2:47 PM, Florian Müller <fm...@apache.org>
> wrote:
>> Hi Michael,
>>
>> For versionable documents this check is correct. For non-versionable
>> documents the spec allows using the same Version Series Id for
>> multiple
>> documents. I have changed the check from reporting a failure message
>> to an
>> info message in this case.
>> However, we have seen clients that used the Version Series Id to
>> correlate
>> documents without checking if they are versionable or not. Those
>> applications get confused when they find that all non-versionable
>> documents
>> belong to the same version series. Therefore, repositories should
>> always
>> provide a unique Version Series Id, even if the spec doesn't require
>> it.
>>
>> - Florian
Re: tck - versionSeriesId
Posted by Michael Brackx <mi...@gmail.com>.
Hi,
Are there any other recommendations for servers for use with real world clients?
Michael
On Wed, Mar 13, 2013 at 2:47 PM, Florian Müller <fm...@apache.org> wrote:
> Hi Michael,
>
> For versionable documents this check is correct. For non-versionable
> documents the spec allows using the same Version Series Id for multiple
> documents. I have changed the check from reporting a failure message to an
> info message in this case.
> However, we have seen clients that used the Version Series Id to correlate
> documents without checking if they are versionable or not. Those
> applications get confused when they find that all non-versionable documents
> belong to the same version series. Therefore, repositories should always
> provide a unique Version Series Id, even if the spec doesn't require it.
>
> - Florian
Re: tck - versionSeriesId
Posted by "Huebel, Jens" <j....@sap.com>.
I don't think that this is correct.
The spec says:
"The repository MUST return this property with a non-empty value if the
property filter does
not exclude it. Version property values are repository-specific when a
document is defined as
non-versionable."
I personally do not like to set an id for something that does not exist.
But I read this as that the versionSeries must not be empty even if the
document is not versionable.
After the the change in the TCK I have changed the InMemory repository
accordingly-
Jens
On 13.03.13 14:47, "Florian Müller" <fm...@apache.org> wrote:
> Hi Michael,
>
> For versionable documents this check is correct. For non-versionable
> documents the spec allows using the same Version Series Id for multiple
> documents. I have changed the check from reporting a failure message to
> an info message in this case.
> However, we have seen clients that used the Version Series Id to
> correlate documents without checking if they are versionable or not.
> Those applications get confused when they find that all non-versionable
> documents belong to the same version series. Therefore, repositories
> should always provide a unique Version Series Id, even if the spec
> doesn't require it.
>
> - Florian
>
>
>> Hi,
>>
>> On trunk the tck now checks that versionSeriesId's are different for
>> multiple new documents.
>> However, my understanding is that the versionSeriesId is repository
>> specific if the document is not versionable.
>> For example it could use "none" for all documents.
>> Should the check not be conditional on versionable attribute of the
>> type?
>>
>> Michael
>
Re: tck - versionSeriesId
Posted by Florian Müller <fm...@apache.org>.
Hi Michael,
For versionable documents this check is correct. For non-versionable
documents the spec allows using the same Version Series Id for multiple
documents. I have changed the check from reporting a failure message to
an info message in this case.
However, we have seen clients that used the Version Series Id to
correlate documents without checking if they are versionable or not.
Those applications get confused when they find that all non-versionable
documents belong to the same version series. Therefore, repositories
should always provide a unique Version Series Id, even if the spec
doesn't require it.
- Florian
> Hi,
>
> On trunk the tck now checks that versionSeriesId's are different for
> multiple new documents.
> However, my understanding is that the versionSeriesId is repository
> specific if the document is not versionable.
> For example it could use "none" for all documents.
> Should the check not be conditional on versionable attribute of the
> type?
>
> Michael