I think by design, separating the task of escaping
entities makes the c:url action change proof.
By this I mean, irregardless of whether it's HTML4.0
which requires the un-escaped version of the ampersand
or if it's XHTML1.0 which requires an escaped version
or if suppose something new (XML2.0, XHTML2.0) came up
and instead of & if it required say a
hexadecimal/unicode version of ampresand then c:url
would have to change every time an XML spec or some
other dependent spec changed.
By keeping it in the basic form (unescaped ampersand),
we can use c:out to change it to anything else.
Also c:redirect requires an unescaped version of the
ampersand.
-Regards
Rashmi
--- Mikolaj Rydzewski <[EMAIL PROTECTED]> wrote:
> Rashmi Rubdi wrote:
> > There is a way to get the escaped ampersand with
> >
> > c:url and c:out when you set the escapeXml
> attribute
> > of c:out to true, it converts the & to &
> >
> Yes, you're right. I haven't thought about this
> solution. But I prefer
> shorter version: ${someURL} insetad of <c:out ...
>
> Anyway, thanks.
>
> --
> Mikolaj Rydzewski <[EMAIL PROTECTED]>
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
