Difference between revisions of "MoDisco/Components/JSP/Architecture/0.9"
|Line 1:||Line 1:|
Revision as of 07:53, 7 September 2010
|Mailing List • Forums|
|Browse Source • Project Set File|
Modisco JSP Parser has been developed using an ANTLR grammar.
It can support JSP file, as well as HTML files, TAG files, and JSP/TAG fragment files
The ANTLR grammar is composed with rules representing what could be founded in a JSP file :
The root element for the grammar is "Page", which is basically a JSP file.
A "Page" can contain JSP items, as well as Doctype declarations, comments, CData items or simply HTML tags
Tags are the basic elements to describe a JSP file. A tag can contain xml-like attributes, possibly composed with JSP elements.
Updating the Grammar
Non XML Conformity
In order to build the inheritance tree, we had to store all the found tags, and each time a closing one is detected, rebuild the inheritance tree.
This fragment of code will add the <img> tag to the children of the <p> tag when </p> is detected, and so on.
User Code in the generated one
Because we do not know if a tag will be closed later in the code, we had to manually implement some text concatenation.
Let's say we meet a new opening tag:
This is some HTML content
We cannot declare a rule "'<p>' 'any letter' '</p>'" because </p> might never appear, or a JSP expression could be there. That is why we concatenate manually the potentially present content after an opening tag, and wait till we found a known token.