I, too, had issues with this. After time with a sniffer and looking
at apache access_log, I came up with the following:
file: /etc/httpd/conf.d/gwt.conf
ProxyPass /gwt/ ajp://localhost:8009/gwt/
<Directory /var/www/html>
RewriteEngine on
RewriteBase /
RewriteCond %{REQUEST_URI} !(gwt/)(.*)
RewriteRule ^(.*)$ gwt/$1
</Directory>
And then in my html host page I used:
<script type="text/javascript" language="javascript" src="WarGwt/
WarGwt.nocache.js"></script>
I discovered that the issue is ProxyPass and ProxyPassReverse, not
being like squid, pass through the fully-qualified URL in the rpc
without adding the gwt/ that the policy on tomcat expects. If I used /
WarGwt/WarGwt.nocache.js it would be found but then development mode
would break. The relative path seems to do the trick since when the
page is served, it gets served by tomcat as /gwt/WarGwt/
WarGwt.nocache.js and when the RPC is generated in the client, it has /
gwt/ in it.
This was definitely a headache.
Davek
--
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.
