We solved this by extending RemoteServiceServlet and overriding
doGetSerializationPolicy.
This method has a Parameter for the moduleBaseURL. We check if the
moduleBaseURL starts with www.ourdomain.com/proxyname/appname and replace
it with www.ourdomain.com/appname prior to the super.
We solved this by extending RemoteServiceServlet and overriding
doGetSerializationPolicy.
Thie method has the moduleBaseURL as a parameter. We replace the
moduleBaseURL coming in as www.domain.com/proxyname/appname with
www.domain.com/appname and call *super*.doGetSerializationPolicy. This way
Is anybody knows what are the supported browser version for GWT 2.7? In GWT
official page they listed link
http://www.gwtproject.org/doc/latest/FAQ_GettingStarted.html#Browsers_and_Servers
,
but i dont no for which GWT version this browser will support.Any help?
--
You received this message
Any chance someone from the steering committee could comment on this?
On 3 August 2015 at 09:37, maticpetek maticpe...@gmail.com wrote:
1+
On Friday, July 31, 2015 at 11:39:00 AM UTC+2, James Horsley wrote:
Firstly, I am very much looking forward to the next generation j2cl
compiler for
Am trying to provide public access to a back end GwT app running on back
end private cloud server going through an Apache httpd server as front end
proxy.
I can ProxyPass via AJP or HTTP, but when I try to load the app, I get an
XSRF error on the first call as the module path requested is not
*GWT 2.8 release is delayed* for couple of months already, though
development is still going on in GWT master branch on GitHub
https://github.com/gwtproject/gwt/commits/master.
Has anybody heard *any news from GWT team* recently?
Ironically, couple of weeks ago one of our teams chose AngularJS
