Heiko I am this and next week on travel, but will look as soon as possible in this issue.
Jens -----Original Message----- From: Kiessling, Heiko [mailto:[email protected]] Sent: Montag, 12. September 2011 10:45 To: [email protected] Subject: RE: Issues with org.apache.chemistry.opencmis.server.support.query.QueryUtil.traverseStatementAndCatchExc Hi, Jens, thanks for your quick reply. I got me the snapshot 'chemistry-opencmis-server-support-0.5.0-20110911.030458-142.jar' in the meantime but this has still the problem with the eascaping mechanism. The WHERE clause I try is 'WHERE cmis:name LIKE 'Do\\%ent''. Thanks and best regards Heiko ---------------- You wrote: Hi Heiko, are you using the latest snapshot from SVN? Since the last release there are several fixes and enhancements to the escaping mechanism. Please use the latest version from the trunk if you don't have it and let me know if this still does not work as expected. (A new release will be available soon). There is no kind of semantic analysis in the framework. It is just the parser and any error handling except basic syntax errors is up to you. Hope this helps.... Jens -----Original Message----- From: Kiessling, Heiko [mailto:[email protected]] Sent: Mittwoch, 7. September 2011 18:23 To: [email protected] Subject: Issues with org.apache.chemistry.opencmis.server.support.query.QueryUtil.traverseStatementAndCatchExc Hi, in the cause of implementing CMIS queries I have found the following problems with the above method: - The parser does not accept escaping backslashes in LIKE strings. For example, the string 'pa\%ern' which according to the CMIS spec is supposed to look for the value 'pa%ern' is acknowledged with the two messages "mismatched character '%' expecting set null" and "mismatched character '<EOF>' expecting '''" and a CmisInvalidArgumentException. Sounds like a lexical analysis problem to me. - Is there semantic analysis built in? For example, the = ANY operator is not possible for single-valued properties, and, vice versa the simple = operator is not allowed for multi-valued properties. However, no error is announced when parsing this kind of statement. Would be great if you could tell us whether these are known limitations at this time but are worked on, or whether we're making any mistakes. Thanks and best regards Heiko Kiessling Senior Developer TIP CORE Conn., Security, Integr. (AG) SAP AG | Dietmar-Hopp-Allee 16 | 69190 Walldorf, Germany T + 49 6227 745434 | F + 49 6227 7822615 E [email protected]<mailto:[email protected]> | www.sap.com<http://www.sap.com/> Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.
