Martin Grotzke wrote:
Hi,
Hi Martin,
I just want to pickup this topic in a new thread, to make sure
it's noticed - thx to Uli's suggestion in the previous thread :)
At first a short summary again:
- T5 (the PageRenderDispatcher) tries to decode activation context
arguments (in convertActivationContext).
[...]
Our encoding is UTF-8 btw.
My question is: why does PageRenderDispatcher.convertActivationContext
try to decode the already decoded string again? I asume there's *some*
reason for this ;)
Sorry to resurrect this old post, but I encounter the very same bug. I
know it is corrected in recent version of T5 (after 5.0.8, I believe)
but for now, I'm stuck with 5.0.6.
So, to bypass it, I contribute to master dispatcher a
PageRenderDispatcher without the double decoding, but now it seems to be
worst :
- it almost work but sometimes (I think it's when I call
ComponentResources#createPageLink or similar methods), spaces are
encoded with "+", but the "+" are not decoded. So, returned link are not
understood by Tapestry, but if a replace "+" by "%20" or " ", everything
works.
- changing the order of utf8filter (with "after:*" or "before:*" in
configuration) doesn't seem to do anything
I believe I forgot to switch a configuration to UTF-8, somewhere. But
I don't know where :/
So, Martin, have you find a way to have it to work ? Have you any idea ?
It's a really important bug for us :/
Thanks,
--
Francois Armand
Etudes & Développements J2EE
Groupe Linagora - http://www.linagora.com
Tél.: +33 (0)1 58 18 68 28
-----------
InterLDAP - http://interldap.org
FederID - http://www.federid.org/
Open Source identities management and federation
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
