OK, now that I understand your process better I can see why you are wondering about these issues! In your case you would want the entire CF system exposed because you're not deploying an application to production, you're delivering an entire system to a customer.
The J2EE packaging might make the delivery / setup process slightly easier but given the "team of consultants" approach it's probably a moot point... On Wed, 9 Feb 2005 09:56:57 -0500, Ben Rogers <[EMAIL PROTECTED]> wrote: > I think our perspectives are different. Some of the software I develop is > deployed in places I will never visit. At those locations, they often have > development, QA and production systems. So, when I "deploy" an app, it's not > straight to production. Deployment for me means that it's going to a > customer's site. > > There's usually 6 months or so between the time the customer sets it up in > development and the time the app goes into production. During that time, > we're determining the best settings for the particular environment. Once > we've set up the development environment, the customer (or on site > consultants) duplicates it as QA environment and then as a production > environment. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:193932 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
