Hello,
I'm new to the list, and for my fist post I have an issue about
autocompleter.
I have an UTF-8 application using tapestry 4.0.2 and tacos-4.0.1. In
this application all the tacos staff is working with UTF-8 except
autocompleter, which return strange not converted characters.
I've been taking a look and I found something interesting. Autocompleter
send a GET request to the web server (I'm using Tomcat 5.5.20). The
first thing tacos does is:
request.setCharacterEncoding("utf-8");
and after that it is supposed all the parameters should be decoded using
this encoding, but it is not (at least for me).
when I try to get a parameter from the request:
request.getParameter("paisOrigen");
It gets me to tomcat's org.apache.catalina.connector.Request
public String getParameter(String name) {
if (!parametersParsed)
parseParameters();
return coyoteRequest.getParameters().getParameter(name);
}
It has never been parsed before so, it gets to the parse staff, which
should decode the parameters.
protected void parseParameters() {
....
if (!getMethod().equalsIgnoreCase("POST"))
return;
...
DECODE STAFF
....
}
So only if the submit method is POST, in my case for autocompleter is
GET, it is decoded.
I'm not sure why autocompleter use GET instead of POST in my
application.... do you have any clue? is this normal?
Thanks
Pedro Ayala
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Tacos-devel mailing list
Tacos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tacos-devel
