Re: T5 Encoding issue (repost)

2008-01-28 Thread Martin Grotzke
On Mon, 2008-01-28 at 18:54 +0100, Francois Armand wrote: > I spoke to fast : it seems that in T5.0.9, even "slashes" are handled > correctly with utf-8 filter activated. This would be really great - then we should take the effort and upgrade... Good luck to you, cheers, Martin On Mon, 2008-01-

Re: T5 Encoding issue (repost)

2008-01-28 Thread Francois Armand
Francois Armand wrote: Are you sure this issue is solved in the latest version of T5? So that you can even have slashes in your activation parameters? Well, you are right : slashes are not supported. But spaces, "+", accented letters are well encoded/decoded I spoke to fast : it seems th

Re: T5 Encoding issue (repost)

2008-01-28 Thread Francois Armand
Martin Grotzke wrote: Hi Francois, we're currently living with a really ugly hack: we use a patched version of TapestryInternalUtils, with the methods urlEncode and urlDecode changed [1]. Ho. Well, I tested almost everything I thought to, and the last item is "patch Tapestry 5.0.6". I really

Re: T5 Encoding issue (repost)

2008-01-28 Thread Martin Grotzke
Hi Francois, we're currently living with a really ugly hack: we use a patched version of TapestryInternalUtils, with the methods urlEncode and urlDecode changed [1]. For us this is still an issue we want to investigate, I believe this is an issue in combination with mod_jk. But my memory is reall

Re: T5 Encoding issue (repost)

2008-01-28 Thread Francois Armand
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 convertAc

T5 Encoding issue (repost)

2007-06-21 Thread Martin Grotzke
Hi, 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). - The activation contex

Re: T5 encoding issue

2007-06-21 Thread Ulrich Stärk
I think you should re-post this issue as another topic so that people notice it. At least in my mail client, this topic is some way down now :) Uli Martin Grotzke schrieb: On Wed, 2007-06-20 at 22:02 +0200, Martin Grotzke wrote: Hi, this is an urgent and important issue for us. Can anybody h

Re: T5 encoding issue

2007-06-20 Thread Martin Grotzke
On Wed, 2007-06-20 at 22:02 +0200, Martin Grotzke wrote: > Hi, > > this is an urgent and important issue for us. Can anybody help > with this? Howard? > > As I wrote below: request.getServletPath() (or request.getPath()) > already provides the decoded path. > a) Should request.getPath() provide t

Re: T5 encoding issue

2007-06-20 Thread Martin Grotzke
Hi, this is an urgent and important issue for us. Can anybody help with this? Howard? As I wrote below: request.getServletPath() (or request.getPath()) already provides the decoded path. a) Should request.getPath() provide the encoded path, or b) should the additional decoding (in PageRenderDi

Re: T5 encoding issue

2007-06-18 Thread Martin Grotzke
On Sun, 2007-06-17 at 23:24 +0200, Martin Grotzke wrote: > I just stepped through the sources to see where the URI get's > decoded to the activation context arguments, and found that the > o.a.t.internal.services.PageRenderDispatcher.dispatch invokes > convertActivationContext with the path info to

Re: T5 encoding issue

2007-06-17 Thread Martin Grotzke
I just stepped through the sources to see where the URI get's decoded to the activation context arguments, and found that the o.a.t.internal.services.PageRenderDispatcher.dispatch invokes convertActivationContext with the path info to convert it to the activation context args. convertActivationCon

Re: T5 encoding issue

2007-06-17 Thread Martin Grotzke
On Tue, 2007-06-12 at 10:38 +0200, Ulrich Stärk wrote: > In case you are using Tomcat try adding URIEncoding="UTF-8" to your > connector definition in server.xml. I just tried that, but it does not solve the problem. I have added a servlet filter that prints the requested uri to the std out, just

Re: T5 encoding issue

2007-06-12 Thread Ulrich Stärk
In case you are using Tomcat try adding URIEncoding="UTF-8" to your connector definition in server.xml. Uli On Mo, 11.06.2007, 23:13, Martin Grotzke sagte: > Hi, > > I have currently an encoding issue, but am not really sure what's > the reason for this. > > I have an url that contains a url enco

T5 encoding issue

2007-06-11 Thread Martin Grotzke
Hi, I have currently an encoding issue, but am not really sure what's the reason for this. I have an url that contains a url encoded german umlaut (ü) in UTF-8 and looks like the following: http://localhost:8080/app/search/%C3%BCbel (the %C3%BC represents the ü in UTF-8, this url is created by c