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 2002/10/18 09:20:36 UTC
DO NOT REPLY [Bug 13757] New: -
[PATCH] null attribute for and encoding unification
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=13757>.
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=13757
[PATCH] null attribute for <esql:get-string/> and encoding unification
Summary: [PATCH] null attribute for <esql:get-string/> and
encoding unification
Product: Cocoon 2
Version: Current CVS
Platform: PC
OS/Version: Linux
Status: NEW
Severity: Normal
Priority: Other
Component: general components
AssignedTo: cocoon-dev@xml.apache.org
ReportedBy: michael.enke@wincor-nixdorf.com
Some definitions for null attribute was going into esql.xsl with an earlier
patch but not completed. This is done with this patch. Make use of this e.g.:
<esql:get-string column="abc" null=""/> to avoid NPE's or
<esql:get-columns null="no value available"/> to have an alternative text.
Further I unified getAscii(...) and getStringOrClob(...) to
getString(...,encoding,...) because with dbClob.getCharacterStream()
we have no control over the encoding.
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org