I have a GWT app using EJB and Glassfish V3. Client-side edits reflect instantly on reload, while server-side changes demand a mode restart. Is there a more efficient method?
hey, i had a simlar issue before. try tinkering with glassfish’s auto-deploy settings or consider jrebel for hot swaping. its not a magic pill but easier than restarting everything each time
hey, have you tried tweaking glassfish to use its incremental deploy option? im wonderin if a hot update plugin might allow backend changes without a full restart. anyone else experminting with this method?
In my experience, configuring an automated deployment process can greatly reduce the wait after server-side changes. I integrated a file watcher with a script that triggers a redeployment when source files are modified, thereby minimizing downtime between changes and test iterations. This method, while not entirely eliminating reloads, cuts down manual intervention and makes the development process smoother. Although it may require initial setup, the efficiency gains and reduced hassle have made it worthwhile in many projects similar to a GWT EJB setup.