commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (JELLY-66) tag body as unescaped xml
Date Thu, 02 Sep 2004 06:40:50 GMT
The following comment has been added to this issue:

     Author: dion gillard
    Created: Wed, 1 Sep 2004 11:39 PM
You can use the core:file tag for this as well.
View this comment:

View the issue:

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

     Status: Unassigned
   Priority: Major

    Project: jelly
             core / taglib.core
   Fix Fors:

   Reporter: Knut Wannheden

    Created: Mon, 28 Jul 2003 2:32 AM
    Updated: Wed, 1 Sep 2004 11:39 PM

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

The following snippet exposes the problem:

<j:set var="foo">

I expected the output to be "<foo></foo>" (or "<foo/>") but it is actually

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 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?

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message