It will still generate the objects in a production environment if they do not exist. You can of course generate them ahead of time and deploy them. We replace reactor with the latest build. Then blow away any project files. I only change the sub classes if the API has changed, and that has not been necessary in a while. I allow reactor to write to the project directory and the data directory where the crud objects are stored.
As I stated before you could generate all the objects in a staging environment and deploy them instead of allowing reactor to create them on the fly if your change management team requires as such. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brad Haas Sent: Wednesday, June 21, 2006 10:22 AM To: [email protected] Subject: [Reactor for CF] Workflow question 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/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- **************************************************************************** This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. **************************************************************************** -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
