On Thu, 13 Dec 2001, Ragy Eleish wrote: > Write a tool based on the Jasper code line to convert normal JSPs to the XML > view of JSPs (aka JSP Document). This tools should have a two modes; the > first one to convert any JSP to XML view of JSP. The second mode to convert > HTML+JSP to XHTML+JSP document, where it fixes all HTML tags incorrectness > and convert them to XHTML transient format (like an enhanced Tidy).
For the second part, there is also 'jtidy' ( not sure about the licence ). For the first part - the only problem is preserving the line numbers for error reporting ! This problem is common to other systems ( cocoon, probably most translators ). One possible solution is to add a special attribute to the generated XML tags ( in a separate namespace ). Or just make sure you generate with exactly the same line structure. I assume you'll use CDATA for the content ( or translate to >... ) to make sure it is a valid xml ( if the source is not HTML/XHTML ). > Open Questions: > ----------------------- > - Should this tool be a forked from Jasper code line or should Jasper be > modified to add customizations to it? I would vote for the first option. Eventually make it an ant-like bean, so it can be automatized/integrated into ant later. > - Is that an acceptable proposal? If yes, who should I contact to commit to > code to CVS (since I don't have a commit status)? I'm +1 on such a tool, I think it would be quite useful. You'll need to send this as a patch first. Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
