You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by bu...@apache.org on 2003/10/01 09:13:57 UTC
DO NOT REPLY [Bug 23538] New: -
JXTemplateGenerator calls setDocumentLocator() excessively
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23538>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23538
JXTemplateGenerator calls setDocumentLocator() excessively
Summary: JXTemplateGenerator calls setDocumentLocator()
excessively
Product: Cocoon 2
Version: Current CVS 2.1
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: sitemap components
AssignedTo: dev@cocoon.apache.org
ReportedBy: samc@atnet.net.au
In the execute() and executeRaw() methods of JXTemplateGenerator, the output for
the next consumer in the chain is produced by iterating over the list of events
created previously when the generator parses its' input. For every iteration of
this list, the setDocumentLocator() method on the consumer is called.
IIUC the API documentation for consumers, this call only makes sense before
startDocument() and not while other SAX events are being passed. I can't quite
see what untoward effects this has - however fixing this behaviour somehow put
an end to problems I was having using JXFormsGenerator which was in turn using a
JXTemplateGenerator pipeline to generate the form definition.