It's definitely a problem.
<j:set var="xx">${expr}</j:set> escapes and <j:set var="xx"
value="${expr}"/> doesn't
;-(
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
"Wannheden, Knut" <[EMAIL PROTECTED]> wrote on 18/03/2003 08:40:19
PM:
> I never got a conclusive answer to this problem I posted a few weeks
ago. A
> proposed solution was to use the "encode" attribute of the <j:set/> tag,
but
> it doesn't have any effect for some reason. So maybe it's a bug in
Jelly?
>
> To restate the problem: If I set a variable to some XML data and later
> dereference this variable, the output is escaped using XML entities. I
> would like the output to be in unescaped form. I have tried the
following:
>
> <j:jelly xmlns:j="jelly:core">
> <j:set var="foo" encode="false">
> <bar/>
> </j:set>
> ${foo}
> </j:jelly>
>
> but despite the "encode" attribute is set to false the output is
> "<bar></bar>". And I'd like it to be "<bar></bar>" (or
> "<bar/>").
>
> Cheers,
>
> --
> knut
>
> > > > 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.
> > >
> >
> > Doesn't seem to work for me (using CVS version)... No matter if I set
> > "encode" to true or false, the outcome of the script:
> >
> > <j:jelly xmlns:j="jelly:core">
> > <j:set var="foo" encode="false">
> > <bar/>
> > </j:set>
> > ${foo}
> > </j:jelly>
> >
> > is always "<bar></bar>". Am I missing something
> > else here?
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]