> Thanks for the reply and information, it sounds like there is a workaround > then for the GWT part but we still have the same/similar issue with > Tomcat's authentication. We need to solve that too else its only a partial > solution. >
I am not familiar with tomcat and your overall setup but it sounds like your session cookie might not be correct during authentication and you reach some login timeout. Maybe Tomcat sets a JSESSIONID cookie for localhost when accessed through the proxy. Thats why I said you might need to rewrite cookies in your proxy. Btw, regarding the GWT serialization issue...I read online some say a way > around this is to use IsSerializable instead of Serializable to mark > objects going across the wire but its not clear if that 'trick' still works > or not. Also some say to drop GWT RPC and use JSON instead that doesn't > have the same issue. I don't really care what the format of the data is > going across the wire, I just need the results to work. Is there an easy > way to switch the RPC format to JSON or some other format that doesn't have > this issue? > When you use IsSerializable then GWT will fallback to an old serialization policy which does not require a RPC policy file. I am not very familiar with that old serialization policy but it is considered legacy. You can not change the way GWT-RPC works but you could stop using GWT-RPC and switch to REST / JSON using https://resty-gwt.github.io . As its API on client side is pretty similar to GWT-RPC it should be easy to migrate. On server side you would use some JAX-RS 2.0 implementation like Jersey or RESTEasy (or others). -- J. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
