I had a similar problem with a WebSeal reverse proxy. Some proxies
will change the context root of application thus making GWT
serialization policy unhappy. The way handled it was to configure a
transparent junction in WebSeal. I don't know if Apache reverse proxy
behaves the same. Hope it helps.
On 26-Feb-10, at 10:40 AM, Fabiano wrote:
@siberian
If you have changed nothing in the code I think the problem is in the
script call.
1) Please check:
Have you changed (in the script calling address) the relative path to
"I don't know the name" path.
example : /myapp/nocache.js to myapp/nocache.js or absolute
http://myapp/nocache.js
this shouldn't be the problem but... who knows
Ps:what is your gwt version ? What about your developemente
enviroment(AS, OS)?
--
You received this message because you are subscribed to the Google
Groups "Google Web Toolkit" group.
To post to this group, send email to [email protected]
.
To unsubscribe from this group, send email to [email protected]
.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en
.
--
You received this message because you are subscribed to the Google Groups "Google
Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
