简体繁体 English

我们可以将Java EE war文件部署到Google App Engine而不进行任何更改吗？

[英]Can we deploy a Java EE war file to Google App Engine without any changes?

原文 2016-03-14 11:02:05 1 1 java/ google-app-engine/ google-cloud-platform

Hi I have a jee application(war file) running on tomcat 7 and mysql 5.5. 嗨我有一个在tomcat 7和mysql 5.5上运行的jee应用程序（war文件）。 Can i run the same war file on google-App-Engine without any modifications? 我可以在google-App-Engine上运行相同的war文件而不做任何修改吗？ If so how? 如果是这样的话？

1 个解决方案

No, you cannot. 你不能。 At minimum App Engine requires configuration file named appengine-web.xml. App Engine至少需要名为appengine-web.xml的配置文件。

In addition to the web.xml deployment descriptor, an App Engine Java application uses a configuration file, named appengine-web.xml, to specify the app's registered application ID and the version identifier of the latest code, and to identify which files in the app's WAR are static files (like images) and which are resource files used by the application. 除了web.xml部署描述符之外，App Engine Java应用程序还使用名为appengine-web.xml的配置文件来指定应用程序的注册应用程序ID和最新代码的版本标识符，并识别其中的哪些文件。 app的WAR是静态文件（如图像），它们是应用程序使用的资源文件。

Beside that it depends on your application requirements. 除此之外，它取决于您的应用要求。 App Engine offers two environments - sandboxed and Maneged VMs . App Engine提供两种环境 - 沙盒和Maneged VM 。 In case of sandboxed environment there are other restrictions you have to take into account: 如果是沙盒环境，您还必须考虑其他限制：

Read-only access to the filesystem 对文件系统的只读访问权限
60s request limit (in case of automatic scaling type) 60s请求限制（在自动缩放类型的情况下）
32 MB request/response size limit 32 MB请求/响应大小限制
Subset of the JRE classes (The JRE Class White List) JRE类的子集（JRE类白名单）
Threads can't “outlive” the request that creates them 线程不能“比”创建它们的请求“寿命”
Max 50 concurrent threads per request 每个请求最多50个并发线程