The following comment has been added to this issue:

     Author: dion gillard
    Created: Mon, 6 Sep 2004 9:16 PM
       Body:
Do we have tests for the set tag and it's encode attribute?
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/JELLY-66?page=comments#action_52898

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JELLY-66

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JELLY-66
    Summary: tag body as unescaped xml
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: jelly
 Components: 
             core / taglib.core
   Fix Fors:
             1.0

   Assignee: 
   Reporter: Knut Wannheden

    Created: Mon, 28 Jul 2003 2:32 AM
    Updated: Mon, 6 Sep 2004 9:16 PM

Description:
(I've reported this problem to commons-user before.  See thread "[jelly] body as 
unescaped xml".)

The following snippet exposes the problem:

<j:set var="foo">
   <foo/>
</j:set>
${foo}

I expected the output to be "<foo></foo>" (or "<foo/>") but it is actually 
"&lt;foo&gt;&lt;/foo&gt;".

The problem is that there is no way to control this behaviour.  The reason is that the 
factory methods of XMLOutput by default return an instance which escapes body text 
with XML entities (as in the example).  In many applications this makes sense, but ss 
Jelly is primarily a tool to manipulate XML, I think the default should be _not_ to 
escape XML.  (Also read the discussion in http://www.mail-archive.com/[EMAIL 
PROTECTED]/msg02750.html.)

In the example the variable "foo" actually gets assigned the String value 
"<foo></foo>", which is escaped when it's dereferenced using "${foo}".  The question 
is whether the value should really be a String.  Shouldn't it really be XML?


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to