gsp - How does one make a Grails application designer friendly without the need to re-deploy after a change to the view? -


It has been for a long time since I actually worked with J2EE, please excuse my ignorance . My recent engagement in a Grails project has increased once more and especially my interest in Java in Grails because it is being said that Java platform redesigns web applications on fun, I need a specialist to have the following I would like to comment on that I have an app using Grails:

Design team (web designer) needs access to GSP pages And visual files have to be edited (software developers) without disturbing (layout, template, etc.) this scenario can occur during the construction and during the production deployment.

The communication level between designers, developers and business users is not an issue here. However, about 40% of the time, Business Unions included request changes in the front-end, which had no effect on the timers of developers, but the timing of a member of the Design Team is required. Currently, the deployment workflow follows Grails App through the deployment of a war file on the Tomcat server. I imagine that the design team is an easy way to allow UI to make changes without creating and deploying the lifecycle.

Many design team members have contacted previous and sometimes PHP with the ability to overwrite only one template file to make a UI piece more functional or to improve layout templates. I hope there is a similar way of adjusting such simplicity within Grails. I've been told that blasting a war file can be an option, but there is still a need to reload the hosted hosted by Tomcat.

If you think I am seeing the desired solution wrongly, please, since I am more interested in making a practical agreement for all the team members involved in this thanks. You can run a server with a version of application through Run-Ape in development mode

Are there. Designers can then change ideas and they will reload. They have to be able to get the source code on the server through some kind of part. Plus, if you have checked the source, then you can make changes to the designer server.

The downside is that if you fail to reload or you go out of memory (due to many, known to be reloaded) either stop a developer and The app will need to start or you can provide designers with a script to run it to bounce.

You will obviously walk in development mode and hit the show and run-through the app, but this can be fine business in your case.

Cheers

Lee


Comments

Popular posts from this blog

oracle - The fastest way to check if some records in a database table? -

php - multilevel menu with multilevel array -

jQuery UI: Datepicker month format -