commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (JELLY-155) body not correctly parsed
Date Mon, 11 Oct 2004 04:00:51 GMT
The following comment has been added to this issue:

     Author: Hans Gilde
    Created: Sun, 10 Oct 2004 9:00 PM
I've been looking into the XML tag libs becuse of the probelm in JELLY-148. There are a few
inconsistencies in the XML tags related to choosing between parsing the output of child tags
and just letting them output XML directly to the XMLOutput. Currently, not all the XML tags
use the ParseTagSupport properly.

I'll double check the solution to this issue while I'm finishing the patch for JELLY-148.
View this comment:

View the issue:

Here is an overview of the issue:
        Key: JELLY-155
    Summary: body not correctly parsed
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: jelly

   Reporter: Michael Altenhofen

    Created: Fri, 8 Oct 2004 12:50 AM
    Updated: Sun, 10 Oct 2004 9:00 PM

In the current version (1.6) of ParseTagSupport the code of parseBody may generate an empty
document, especially if the body is generated by a nested jelly tag.
Looks like there is nobody notifying the writer that new tags are found, so the writer simply
ignores any data that is written out thus producing and empty document.

Replacing the method body with 

              return parseText(getBodyText(false));

seems to do the trick.

This issue has also been posted to the bugzilla tracking system (BUG # 31534), but I was advised
to post it here again.

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