You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Magnus Kvalheim (Created) (JIRA)" <ji...@apache.org> on 2011/12/13 21:57:30 UTC
[jira] [Created] (TAP5-1789) Live reload in production
Live reload in production
-------------------------
Key: TAP5-1789
URL: https://issues.apache.org/jira/browse/TAP5-1789
Project: Tapestry 5
Issue Type: New Feature
Components: tapestry-core
Affects Versions: 5.3
Reporter: Magnus Kvalheim
Tapestry 5.2.x allowed for production reload, but this option has been removed in 5.3.
The assumption is that war artifacts are deployed and never modified in production.
A, not uncommon, usecase we have is when design/pr suddenly wants a small update to a single page template - like a banner.
The process of actually making even minor changes to a running webapp is typically commit->build->redeploy. For some containers its safest to also do a cold restart of the server.
It can also cause downtime in service - so redeploy is then delayed to low-traffic hours.
In 5.2 we could make the change 'instantly'.
Seems like template reloading is highly desired
http://tapestry.1045711.n5.nabble.com/Live-reload-in-production-td4313825.html
Howard
"For 5.4, we can introduce yet another level of indirection that
indicates that live reloading is desired in production mode; perhaps
an enum to define what gets reloaded."
Personally I'd be happy just to get template reload...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira