Monday, August 30, 2010

Re: Property value with accent & requestFactoryServlet

Thank you for your answer.
The issue is not fixed on the scaffold demo 2.1M3.
I've submitted it here: http://code.google.com/p/google-web-toolkit/issues/detail?id=5238
Bye for now,
Julien

On Aug 27, 3:21 pm, Thomas Broyer <t.bro...@gmail.com> wrote:
> On 27 août, 15:03, julien <devn...@ac-rennes.fr> wrote:
>
>
>
> > Hi all,
>
> > With the scaffold demo app and using IE8,
>
> > Creating a new employee by entering é as name makes the app crash.
>
> > When the employee list is refreshed, the following exception appears
> > and the list is never shown.
> > Uncaught exception escaped
> > com.google.gwt.core.client.JavaScriptException: (SyntaxError): '}'
> > attendu
> >  number: -2146827279
> >  description: '}' attendu
> >     at
> > com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChann elServer.java:
> > 237)
> >     at
> > com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java:
> > 126)
> >     at
> > com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:
> > 552)
> >     at
> > com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject(ModuleSpace.java:
> > 269)
> >     at
> > com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject(JavaScriptHost.j ava:
> > 91)
> >     at com.google.gwt.core.client.impl.Impl.apply(Impl.java)
> >     at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:214)
> >     at sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source)
> >     at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp l.java:
> > 25)
> >     at java.lang.reflect.Method.invoke(Method.java:597)
>
> > By the way on firefox the
> > accentued character provided by
> > requestFactoryServlet are not displayed even if the character is taken
> > from a utf-8 source
> > file.
>
> > Can you confirm this issue can be reproduced ?
>
> Yes, we have it too, this is because RequestFactoryServlet doesn't set
> the content-type and encoding of the response, so it defaults to "text/
> plain" (and "text/*" with no encoding specified defaults to ISO-8859-1
> per the HTTP/1.1 spec).
> This has been fixed in 2.1M3 AFAICT, but we haven't yet migrated
> (Record.getId having switched to a Long gives us a hard time; we're
> even considering waiting for M4, expecting it'll let us use String –
> or, better yet, any type– again) so I can't tell for sure:http://code.google.com/p/google-web-toolkit/source/diff?r=8466&format...
>
> > Has anybody find a workaround ?
>
> Switch to 2.1M3, or maybe add a servlet filter to force the encoding
> of the response (and maybe also fix the decoding of the request?)

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

No comments:

Post a Comment