Wednesday, October 23, 2013

Re: Failed to get SerializationPolicy when Web Application contains encoded dash

Hi!

We have the same issue but only on a single machine. A war bundle works on my config but not for my collegue.
I'll compare the environments soon: Java, Tomcat, browser, language settings, anything else that might be relevant?

Any ideas what causes this?

Best,
  András

On Thursday, 18 July 2013 07:54:01 UTC+2, Henning Bredel wrote:
Is there anything I might have missed here? 

I can't imagine nobody of you experts stumbled over such problem so far.

Thanks

  Henning

Am Donnerstag, 11. Juli 2013 10:11:44 UTC+2 schrieb Henning Bredel:
Hey Folks,

how can I configure GWT web applications containing an encoded dash ('-' gets %2D in some browser calls) to not fail when getting the SerializationPolicy.

I get this for example:

INFO: MySuperService: ERROR: The module path requested, /super%2Dwebapp/client/, is not in the same web application as this servlet, /super-webapp. Your module may not be properly configured or your client and server code maybe out of date.

If I do miss something or overlooked some basics in the documentation please point me to the right resource.

Thanks in advance.

  Henning

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.

No comments:

Post a Comment