I'm not sure but I think the tomcat bundled with jboss 3.2.5 behaves differently regarding url encoding. I seem to remember some issue with it. Could you test the standalone tomcat version 5.0.x, and confirm that it works or not. I think jboss 3.2.5 requires a different hack in fixTomcatURL not just removing it nor changing the encoding in getBytes().
PostgreSQL database with unicode encoding should work fine, we have tested jboss 4.0/postgres with utf-8 file names.


Carlos

Serkan Ãzkan wrote:
hi again,
first of all thanks for your interest and rapid replies.
but I still have the problem :) I changed tomcat connector URIEncoding. I restarted jboss, redeployed
original slide distribution(without my modifications) , but the problem still exists.
by the way as I wrote in my first message I had added debug code to
service method of WebdavServlet and printed request parameters, and
they were encoded properly. for example Ä (g with hyphen) is encoded
as %c4%9f as it has to be. but after slide processes it is broken.


and another thing regarding my first message, I not only commented fixTomcatURL and fixTomcatHeader, I had also modified them to use
always utf-8 instead of Configuration.urlEncoding().


As a result although request parameters are urlencoded correctly, and
I fixed TomcatURL and fixTomcatHeader to use always utf-8, there are
problems with the filenames.
I also greped slide source to for "encod" and "getbytes" strings and
tried to find a related piece of code but I could not :)
I am using windows xp(english), tomcat bundled with jboss 3.2.5,
commons httpclient to connect slide servlet, my application and slide
are deployed on the same jboss on my computer(xp), postgresql on an
other linux box, etc etc.
and another question, if I change tomcat URIEncoding, does not this
affect all applications deployed on the same tomcat? how does this
affect applications using encodings other than utf-8?

thanks for all

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to