On 2/4/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
> this has to be fixed different later on.
> Because this is horrible. Everywhere we have those special url encoding char
> replacing
> of urls. That should go into one place (at moment of constructing and
> rendering the url)
If that is possib
this has to be fixed different later on.
Because this is horrible. Everywhere we have those special url encoding char
replacing
of urls. That should go into one place (at moment of constructing and
rendering the url)
johan
On 2/2/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
Fixed, see http:
Fixed, see http://issues.apache.org/jira/browse/WICKET-251
Eelco
On 1/23/07, Kadir Sener GUMUS <[EMAIL PROTECTED]> wrote:
> Hi all,
> i experienced a problem with "href" attribute of rendered ExternalLink.
> In our application, i needed to parse rendered html in a SaxParser
> implementation. But
Hi all,
i experienced a problem with "href" attribute of rendered ExternalLink.
In our application, i needed to parse rendered html in a SaxParser
implementation. But i couldnt! When i looked in source codes of
ExternalLink and Link, i saw the problematic line is that, in ExternalLink
there is no
