I'm trying to get a grasp on the workflow process when upgrading to
new versions of Reactor. Normally, here is my process:
(1) Replace Reactor with the latest build.
(2) Blow away all previous files that were generated by Reactor.
(3) Flush the application scope.
The problem I'm having is that I'm not quite sure to handle this in a
production environment. In a development environment, Reactor will
regenerate all the DAOs, Gateways, etc. when they are called. From
what I understand--in production mode this does not happen (or it
happens in a different way). So, how should I handle these types of
upgrades on a production site. I guess I could use the generator to
generate everything to upload to the production site, but I take it
that this will not officially be supported in future releases.
I'd like to find out how most of you handle this or if I have some
misconceptions on how Reactor generates objects.
Thanks,
Brad
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Reactor for ColdFusion Mailing List
[email protected]
Archives at: http://www.mail-archive.com/reactor%40doughughes.net/
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
