Fred, Good ideas, we'll get to them pronto! Sorry for the messup -- we were trying to keep 1.4 compatibility (1.4 uses JSPs templates that use ww:property, which escapes by default).
-Pat -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fred Lamuette Sent: Wednesday, November 19, 2003 7:45 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] WW2beta2 htmlEncode problem Adding $webwork.htmlEncode to rewrite some values brings a serious problem for me. For instance, when you call $!webwork.htmlEncode($itemKey) in the select.vm template, you seem to think $itemKey is inevitably a string when you have written the htmlEncode method. That's not the case, what about an Integer or a Long result ? Would it be possible to change the htmlEncode method signature, like this one : htmlEncode(Object value) and makes the string conversion by calling XWorkBasicConverter.getInstance().convertValue(null,null,null,null,value ,Str ing.class) ? Bravo for your work. Richard HALLIER Chef de projet [EMAIL PROTECTED] 01.40.12.41.52 www.uniclick.org UNICLICK ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
