On Tue, Dec 23, 2014 at 7:57 PM, Christopher Schultz < ch...@christopherschultz.net> wrote:
> So the web server (serving the HTML) is on one machine and the > application server (responding to the REST requests the GWT client > initiates) are on different machines? So the problem is with > Javascript not being able to make a connection to a server that wasn't > the source of the page? > > Tomcat is on one machine hosting the gwt app (delivering javascript to the client, and on the server side accessing a database, etc). There's another host/server running a jetty process that receives REST calls and does data processing, returns results, etc. We need the client side gwt app to be able to reach the other server as well. Perhaps there's a better way to set this up. > If it's mission-critical, then it's worth spending time on it, right? ;) > I'm not sure if our stuff would qualify but in general, I agree. :) >> Can you operate without this proxy, just to see if the GWT client > >> and GWT server can talk to each other without a problem, even in > >> newer versions of Tomcat? > Hmmm, I suppose I could - I haven't explored what's the latest in this area yet. The thing is.... > > I'd love to get some more information about exactly what the proxy is > doing and why. It's possible that you can get rid of it entirely, or > replace it with something that is not home-grown. In some circumstances, we have to do some load balancing - potentially there's one tomcat/app-server and many jetty REST servers - and handling this is not trivial. We had a group of people who (I think) knew what they were doing evaluate if an off-the-shelf product would work for this and they concluded it would be best to go with a home-grown solution.
