young_matthewd
22 Mar 2007, 11:13 PM
yet another encoding ISO-8859-1 problem...
this a server thing and hoping somebody on the forums uses weblogic (8 or higher). using DWR to pump out Spring services to Javascript libraries. so my communication isn't YAHOO.Connect rather the DWR engine. the response/request headers in firefow are as follows:
Response Headers
Date Fri, 23 Mar 2007 07:13:03 GMT
Content-Length 480
Content-Type text/plain
X-Powered-By Servlet/2.4 JSP/2.0
Request Headers
Host localhost:7003
User-Agent Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Accept text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language sv
Accept-Encoding gzip,deflate
Accept-Charset ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive 300
Connection keep-alive
Content-Type text/plain
Content-Length 255
Pragma no-cache
Cache-Control no-cache
which shows that the response has no character set (likely defaults to UTF-8). have added an input-charset directive to the weblogic.xml file (web app level). no change. have added webapp.encoding.default setting to the weblogic-application.xml file (enterprise app level). no change. have altered the default local to sv instead of en at app server startup. no change.
have posted a question on bea's site (http://forums.bea.com/bea/thread.jspa?threadID=400002201&tstart=0&mod=1174632022873). no answer (as usuall).
main problem is that handling encoding/charset isn't a j2ee standard. this type of stuff should be handled in web.xml and mainstream across containers.
any help/ideas are greatly appreciated.
this a server thing and hoping somebody on the forums uses weblogic (8 or higher). using DWR to pump out Spring services to Javascript libraries. so my communication isn't YAHOO.Connect rather the DWR engine. the response/request headers in firefow are as follows:
Response Headers
Date Fri, 23 Mar 2007 07:13:03 GMT
Content-Length 480
Content-Type text/plain
X-Powered-By Servlet/2.4 JSP/2.0
Request Headers
Host localhost:7003
User-Agent Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Accept text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language sv
Accept-Encoding gzip,deflate
Accept-Charset ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive 300
Connection keep-alive
Content-Type text/plain
Content-Length 255
Pragma no-cache
Cache-Control no-cache
which shows that the response has no character set (likely defaults to UTF-8). have added an input-charset directive to the weblogic.xml file (web app level). no change. have added webapp.encoding.default setting to the weblogic-application.xml file (enterprise app level). no change. have altered the default local to sv instead of en at app server startup. no change.
have posted a question on bea's site (http://forums.bea.com/bea/thread.jspa?threadID=400002201&tstart=0&mod=1174632022873). no answer (as usuall).
main problem is that handling encoding/charset isn't a j2ee standard. this type of stuff should be handled in web.xml and mainstream across containers.
any help/ideas are greatly appreciated.