It has been a long time since I really worked with J2EE, so please excuse my ignorance. My recent involvement in the Grails project has further strengthened my interest in Java, and especially in Grails, as it again makes web-based Java platform applications fun. At the same time, I would like the expert to comment on the following requirement that I have for an application created using Grails:
The development team (web designers) requires access to the GSP pages and edits view files (layouts, templates, etc.) without disturbing developers (software developers). This scenario can take place both during construction and after its deployment.
The level of communication between Designers, Developers and Business Users is not a problem here. However, in about 40% of cases, the involved business units request changes in the interface that do not affect the development time, but require the time of a Design Team member. Currently, the deployment workflow follows the Grails application by deploying the War file on the Tomcat server. I assume there is an easier way to let the Design team make user interface changes without going through the build and deployment life cycle.
Some of the design team members have experienced PHP in the past, and sometimes miss the opportunity to simply overwrite the template file to make the user interface element more functional or to improve the layout template. I hope that such an approach will correspond to such simplicity in Grails. I was told that hacking a War file might be an option, but it still requires a reboot of the hosted Tomcat application.
If you think that I am looking at the right solution incorrectly, I ask you to call back, because I'm more interested in an effective compromise for all involved team members. Thanks.
source
share