RE: Java side Util.setValue problem after upgrading to DWR 2.0 RC1

 

Hi,

 

  I still have this problem with DWR2 RC2 when calling setValue from JavaAPI.

Generated HTML is still escaped, even when I put false as a third parameter.  

 

dwr.util.setValue with { escapeHtml:false } works fine, but I can not get the same

effect when calling setValue from Java API. 

Is this a bug or am I doing something wrong when calling Java API ?

Thanks, 

Nemanja

 

 

 

 

---

From: joseph.walker-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx [mailto:joseph.walker-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx] On Behalf Of Joe Walker
Sent: Friday, January 05, 2007 12:08 PM
To: users-EyPigyGktj4FDOXUYO6UHQ@xxxxxxxxxxxxxxxx
Subject: Re: [dwr-user] Java side Util.setValue problem after upgrading to DWR 2.0 RC1

 

In DWR 2.0 rc1 the default changed from HTML being NOT escaped by default, and you set escapeHtml=true TO (in RC1) you get the escaping by default, and setting escapeHtml=false

The same is true of the Java API.

Joe.