cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 10242] - [DOC] Text serializer is not documented
Date Thu, 27 Jun 2002 06:43:15 GMT
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=10242>.
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=10242

[DOC] Text serializer is not documented





------- Additional Comments From j3322ptm@yahoo.de  2002-06-27 06:43 -------
I don't think documentation is sufficient. The problem is that people
develop XSL transformations whit output method="text" which work in other
environments (I did so), and which suddenly stop working when plugged into
Cocoon *without* *any* *notification* on what was wrong. You get a "document
has no content" in the browser, and absolutely no indication in the logs
even if DEBUG is set that the text was dropped. Even people which know XML
processing well might not be aware that using text producing XSLT from Cocoon
changed the rules, and that their style sheets have to produce well formed
XML even if the result is intended to be serialized as text.
Repeat: the XSLT works with a command line processor and in other servlet
environments. There is no indication why it possibly didn't work in Cocoon.
This makes this kind of bugs *very* hard to track down, whether this
peculiarity is well documented or not.
I don't think a Cocoon user should have to do any other steps than setting
log level to debug in order to get notices of dropped text, at least at the
text serializer input.

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message