I think he could just take a look at the Strings class(1.3), and make a
workaround .. That should'nt be that critical...
Another option are to upgrade to 1.3 ... But it's still beta and may
take a day or two depending on complicity of the application(that how
long it took us upgrading a medium application with 70% test coverage
using wicket tester)...
regards Nino
Eelco Hillenius wrote:
It's a nice idea, Eelco. So, should we conclude this thread confirming that
this conversion is not already implemented for Wicket 1.2.6? I mean, do we
need a patch (correction) or do we need an implementation (new
implementation)?
Depends on what you want. Those XML files don't convert to HTML
entities, but I think you don't need that if you properly set the
encodings of your requests/ pages (UTF-8 works best).
Patch works best, even if it is new, because that's just an easy way
to apply to the code base. At this time, it is probably easiest for
you if you create your own branch on wicket 1.2 that does what you
want, as it might take a while before we create a new release for that
(it's pretty much eol as far as we are concerned). Another advantage
to doing that is that you can build exactly what you want without us
having to agree :-)
Eelco
