简体繁体 English

GWT：将客户端和服务器端分为不同的WAR

[英]GWT: Separate client- and server-sides into different WARs

原文 2012-10-20 20:48:52 9 3 java/ google-app-engine/ gwt

I am planning on building a GWT app that will be deployed to GAE. 我正计划构建一个将部署到GAE的GWT应用程序。 In addition to the normal (GWT) web client, the server-side code will service requests from other clients besides just the web app. 除了普通（GWT）Web客户端外，服务器端代码还将为Web应用程序之外的其他客户端请求提供服务。 Specifically, it will host a RESTful API that can be hit from any HTTP-compliant client, and it will also service requests from native apps on iOS and Android. 具体来说，它将托管可从任何HTTP兼容客户端访问的RESTful API，还将为来自iOS和Android的本机应用程序的请求提供服务。

If my understanding of GWT is correct, it's your job to code up both the client-side code (which includes the AJAX requests your app makes back to the server) as well as the server-side request handlers. 如果我对 GWT的理解是正确的，那么您既要编写客户端代码（包括应用程序向服务器返回的AJAX请求），也要编写服务器端请求处理程序。

This got me thinking: why do I need to package the web client and the web server inside the same WAR? 这让我开始思考：为什么我需要将Web客户端和Web服务器打包在同一WAR中？ This forces me to (essentially) re-deploy the client-side code every time I want to make a change to the backend. 每次我想对后端进行更改时，这迫使我（基本上）重新部署客户端代码。 Probably not a big deal, but if I don't have to, I'd prefer to honor "separation of concerns". 也许没什么大不了的，但是如果我没有必要，我宁愿兑现“关注点分离”。

So I ask: is there a way to essentially deploy a Java-less WAR on GAE in such a way that it just serves pure HTML/JS/CSS back to any clients that will use it, and to then deploy the server-side in its own WAR, and some how link the two up? 因此，我想问：是否有一种方法可以在GAE上基本上部署无Java的WAR，使其仅将纯HTML / JS / CSS提供给将要使用它的任何客户端，然后在服务器端部署它自己的WAR，有些如何将两者联系起来？ Thanks in advance! 提前致谢！

3 个解决方案

The WAR is just for the server side. WAR仅用于服务器端。 It includes the client-side classes needed for serializing objects passed between client and server: obviously, both sides need implementations of the same objects in order to handle those objects. 它包括序列化在客户端和服务器之间传递的对象所需的客户端类：显然，双方都需要相同对象的实现才能处理这些对象。

I don't think it will save you any effort or development time to separate the two concerns, but if you really want to, then you can rework your client/server interaction using something other than GWT-RPC. 我认为分离这两个问题不会节省您的精力或开发时间，但是如果您确实愿意，则可以使用GWT-RPC以外的方法来重新进行客户端/服务器交互。 For example, JSON. 例如，JSON。 See https://developers.google.com/web-toolkit/doc/latest/DevGuideServerCommunication#DevGuideHttpRequests for discussion of your options if you want to go down that road. 如果您想走这条路，请参阅https://developers.google.com/web-toolkit/doc/latest/DevGuideServerCommunication#DevGuideHttpRequests以获取有关您的选择的讨论。