You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chemistry.apache.org by "jay brown (JIRA)" <ji...@apache.org> on 2011/05/06 06:11:03 UTC
[jira] [Resolved] (CMIS-363) Property is null!
(AbstractSessionTest.java:1215)
[ https://issues.apache.org/jira/browse/CMIS-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jay brown resolved CMIS-363.
----------------------------
Resolution: Not A Problem
Error was on the server side.
> Property is null! (AbstractSessionTest.java:1215)
> --------------------------------------------------
>
> Key: CMIS-363
> URL: https://issues.apache.org/jira/browse/CMIS-363
> Project: Chemistry
> Issue Type: Bug
> Components: tck
> Affects Versions: OpenCMIS 0.3.0
> Reporter: jay brown
> Assignee: Florian Müller
>
> When testing the openCMIS TCK against our server we see a great many of errors like this:
> FAILURE: Root folder object spec compliance (AbstractCmisTest.java:114)
> FAILURE: Property IndexationId (AbstractSessionTest.java:1215)
> FAILURE: Property is null! (AbstractSessionTest.java:1215)
> INFO: Object is null!
> the offending xml element in our response looks like this:
> <cmis:propertyId queryName="IndexationId" displayName="Indexation Id" localName="IndexationId" propertyDefinitionId="IndexationId"/>
> Since our metadata for this property states that this is not required (required=false), I believe this representation is a valid way to express a 'not set' condition.
> Can we change to TCK to accept this form of a 'not set' property?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira