From: "Wannheden, Knut" <[EMAIL PROTECTED]> > James, > > > This is kinda non intuitive. I think we should probably fix it. > > > > That was my thought too. Especially the <j:set/> tag feels like it should > be transparent in this respect.
Agreed. Indeed I'm not sure how useful the encoding is. > > Basically when XML is output as text it can be encoded into a > > valid XML > > string or left as is. So tags like <j:set> allow XML encoding > > to be turned > > on or off. > > > > <j:set var="bar" encoding="false"> > > <foo/> > > <j:set> > > > > I noticed that <j:set/> has an "encode" attribute, but that's used to encode > stuff like "<" into "&lt;", right? So you propose to add another > attribute "encoding" to control whether to encode data into valid XML text? Sorry I meant the 'encode' attribute. This defaults to true which will encode > into <. So setting this to false will fix your issue. James ------- http://radio.weblogs.com/0112098/ __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
