The following comment has been added to this issue:
Author: Hans Gilde
Created: Thu, 14 Oct 2004 10:36 PM
Body:
While this does solve the problem, it's putting Jelly on a downward slope in terms of
performance. Jelly is supposed to properly output SAX events and isn't supposed to
need to reparse the text coming from child tags. By parsing this text again, we're
just wasting cycles reparsing something that's supposed to be output properly to begin
with.
Michael, is this an immediate problem for you? If not, it'll wait a few weeks while we
fix the XML tags properly.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/JELLY-155?page=comments#action_54137
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JELLY-155
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JELLY-155
Summary: body not correctly parsed
Type: Bug
Status: Unassigned
Priority: Major
Project: jelly
Components:
taglib.xmlunit
Assignee:
Reporter: Michael Altenhofen
Created: Fri, 8 Oct 2004 12:50 AM
Updated: Thu, 14 Oct 2004 10:36 PM
Description:
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.
---------------------------------------------------------------------
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]
