[GROOVY-839] Adding valid xml start and end tags for groovy template scripts

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.0-beta-10
• Component/s: Groovlet / GSP
• Environment: All
• Assignee: sormuras
• Reporter: Al
• Created: 11/May/05 06:17
• Updated: 13/Jul/05 14:19
• Resolved: 13/Jul/05 14:18

Description

Current template scripting (not validxml ):

<%
3.each{println '<p>stooges</p>'
%>

proposed (valid XML) :

<groovy:scriplet>
3.each

{println '<p>stooges</p>'}

</groovy:scriplet>

In addition to avoid additional xml escaping issues use of CDATA I would imagine real world usage :

<groovy:scriplet>
<![CDATA[
3.each

{println '<p>stooges</p>' }

]]>
</groovy:scriplet>

the CDATA enables use of illegal xml characters like '<' and '>' among otehr things.
The implementation of this however should result after templating output as :
<p>stooges</p>

and NOT:
<p>stooges</p>

Otherwise printing of markup on the output of the template will not transpose to an xml output in teh expected fashion!!

I have found otehr ways around this using builders and CDATA section but these are logical or elegant solutions.

For XML compliance on input and output we need the new way.

Issue Links

• is superceded by: GROOVY-952 XmlTemplateEngine must preserve valid XML files
• relates to: GROOVY-782 Provide a xml printer to print Node as xml format