On 06/28/2011 01:56 AM, Howard Lewis Ship wrote:
- reload tml, page classes and implementation classes of specified interface
packages
You want to fund that? It'd be a bit of work.
As I know some of this already exists in development mode, but not sure
to what extent and how configurable it is, or could be made provided
enough time and resources.
This is the scenario that I had in mind:
0. The application is deployed as an exploded war.
1. It goes live in production and you encounter a strange behavior in
some business calculation in specific dao implementation class in just
one method. You have a patch but you don't want to take down the whole
application, only that calculation.
2. So you change the "reloading" parameter - from OFF you switch it to
Reload only implementation classes in the dao.hibernate package and .tml
3. You change the menu tml and hide the respective menu option from users.
4. You change the dao class.
5. Test it on the production, while everything else is live.
6. When satisfied set the "reloading" parameter back to OFF.
How would I do it? I would change the processing for reloading and put
few more conditions if it should be performed or not. But maybe I am
talking non-sense, since I never had a glimpse inside the tapestry
source code, and I don't know if it's doable or not.
But first the question is if this should be attempted at all, since all
of this is extra processing code that could possibly make the production
mode a bit slower.
Second question is how much work could it take to implement this...
Hours? Days? Weeks?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
