You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chemistry.apache.org by Florent Guillaume <fg...@nuxeo.com> on 2010/04/26 20:30:09 UTC
CMISQL parser
Hello,
I've committed the port of the CMISQL parser from Chemistry (see
https://issues.apache.org/jira/browse/CMIS-195).
The idea is that each backend will have to implement an ANTLR3 tree
grammar that makes use of the existing lexer+parser. The
implementation will depend on the internal of the backend of course. I
wrote the start of one for the InMemory server, but it's still pretty
rudimentary as I'm not very familiar with the InMemory implementation.
I don't have immediate plans to work more on it, so feel free... :)
Take note in the pom.xml of the InMemory server how to reuse the
tokens file generated from the generic lexer+parser. This is better
than copying it by hand in your implementation as it may change in the
future if we change things in the generic lexer+parser.
Florent
--
Florent Guillaume, Director of R&D, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87
RE: CMISQL parser
Posted by Jens Hübel <jh...@opentext.com>.
HI Florent,
excellent news!!!
I currently work on finishing the adaption of the new server packages for the in-memory server. Once this is finished (hopefully soon) I will have a look on the integration of your parser.
Jens
-----Original Message-----
From: Florent Guillaume [mailto:fg@nuxeo.com]
Sent: Montag, 26. April 2010 14:30
To: List-Chemistry
Subject: CMISQL parser
Hello,
I've committed the port of the CMISQL parser from Chemistry (see
https://issues.apache.org/jira/browse/CMIS-195).
The idea is that each backend will have to implement an ANTLR3 tree
grammar that makes use of the existing lexer+parser. The
implementation will depend on the internal of the backend of course. I
wrote the start of one for the InMemory server, but it's still pretty
rudimentary as I'm not very familiar with the InMemory implementation.
I don't have immediate plans to work more on it, so feel free... :)
Take note in the pom.xml of the InMemory server how to reuse the
tokens file generated from the generic lexer+parser. This is better
than copying it by hand in your implementation as it may change in the
future if we change things in the generic lexer+parser.
Florent
--
Florent Guillaume, Director of R&D, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87