如何使Grails应用程序设计人员变得友好，而无需在视图更改后重新部署? [英] How does one make a Grails application designer friendly without the need to re-deploy after a change to the view?
问题描述
自从我真正使用J2EE以来已有很长时间了，所以请原谅我的无知.我最近对Grails项目的参与使我对Java尤其是Grails的兴趣再次达到顶峰，因为它再次使在Java平台上构建Web应用程序变得有趣.话虽如此，我希望专家对使用Grails构建的应用程序的以下要求发表评论:
It has been a long while since I have really worked with J2EE so please excuse my ignorance. My recent engagement in a Grails project has peaked my interest in Java once more and especially in Grails as it makes building web applications on the Java platform fun again. That being said, I would like an expert to comment on the following requirement that I have for an application built using Grails:
设计团队(网页设计师)需要访问GSP页面并编辑视图文件(布局，模板等)，而不会打扰开发团队(软件开发人员).这种情况既可以在构造期间也可以在部署到生产中之后发生.
The Design Team (web designers) require access to the GSP pages and edit the view files (layouts, templates, etc.) without bothering the development team (software developers). This scenario can take place both during construction and after deployment into production.
这里，设计人员，开发人员和业务用户之间的通信级别不是问题.但是，大约有40％的时间，所涉及的业务部门要求对前端进行更改，这些更改对开发人员的时间没有影响，但是需要设计团队成员的时间.当前，部署工作流程是通过将War文件部署到Tomcat服务器来遵循Grails应用程序的.我想有一种更简单的方法可以允许设计团队在不经过构建和部署生命周期的情况下进行UI更改.
The communication level between the Designers, Developers, and Business Users are not an issue here. However, about 40% of the time, the Business Units involved request changes to the front-end that have no impact on the Developers time but require the time of a Design Team member. Currently, the deployment workflow follows the Grails application through the deployment of a War file to a Tomcat server. I imagine there is a simpler way to allow the Design team to make UI changes without going through the build and deploy lifecycle.
一些设计团队成员过去曾接触过PHP，有时会错过仅覆盖模板文件以使UI块更有效或改善布局模板的功能.我希望在Grails中也可以采用类似的方式来实现这种简单性.有人告诉我，可以打开War文件，但是仍然需要重新加载Tomcat托管的应用程序.
Several of the Design Team members have had exposure to PHP in the past and at times miss the ability to just overwrite a template file to make a UI piece more functional or improve a layout template. I hope there is a similar way to accommodate such simplicity within Grails. I have been told that exploding the War file might be an option but that still requires the reload of the Tomcat hosted application.
如果您认为我以错误的方式看待所需的解决方案，请保持警惕，因为我对所有相关团队成员的可行折衷方案更感兴趣.谢谢.
If you believe that I looking at the desired solution the wrong way, please do chime in as I am more interested in a workable compromise for all the team members involved. Thank you.
推荐答案
您可以在开发模式下通过run-app运行带有应用程序版本的服务器.然后，设计人员可以对视图进行更改，然后将它们重新加载.他们将需要能够通过某种共享来访问服务器上的源代码.另外，如果您签出了源文件，则设计者可以从服务器提交他们的更改.
You could run a server with a version of the application via run-app in development mode. The designers can then make changes to the views and they will reload. They would need to be able to acccess the source code on the server via a share of some kind. As a plus, if you checked out the source the designers could then commit their changes from the server.
缺点是，如果重新加载失败或内存不足(很多重新加载会导致内存不足)，开发人员可能需要停止并启动应用程序，或者可以向设计人员提供脚本来运行弹起它.
The downside is that if the reloading fails or you run out of memory (has been known to happen with lots of reloading) either a developer would need to stop and start the app or you could provide the designers with a script to run to bounce it.
显然，通过在开发模式下运行和通过run-app运行会对性能造成影响，但在您的情况下这可能是个不错的选择.
You'd obviously take a performance hit by running in development mode and via run-app but it might a ok trade off in your case.
欢呼
李
这篇关于如何使Grails应用程序设计人员变得友好，而无需在视图更改后重新部署?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
