Sorry, but as this is for development I don't think this should be a set in stone thing.
I can deploy a new ear/war, and not want those settings copied across in my development. The only time I would want to copy all my datasource's etc. would be if I was going into a production scenario, but that's me. I am sorry but I would not be advising people that they SHOULD not be using the main instance for development. Regards, Andrew Scott http://www.andyscott.id.au/ > -----Original Message----- > From: Ian Skinner [mailto:[email protected]] > Sent: Tuesday, 17 August 2010 7:49 AM > To: cf-talk > Subject: Re: CFBuilder Server Setup with CF Multiserver Installation > > > On 8/16/2010 2:25 PM, Andrew Scott wrote: > > Laura, where is it written that you should not use the default cfusion > > instance for development? > > The way I read it was that you should not use cfusion if you also plan to > create new instances for other development in the future of other projects. > The reason (as she stated) is that when ever you create a new ColdFusion > instance it will be a clone of the current cfusion instance. > > So, if one where to develop some projects in cfusion, creating DSNs, > mappings, etc. Then create a new instance for another project, that new > project is going to get created with all the settings for the older projects > configured in the cfusion instance. It can be somewhat messy. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:336316 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
