> The original question was a windows specific one (see > subject), so the fact that ColdFusion does not run as a > service is indeed important when starting and stopping (and > is very much an architectural issue when you are accustomed > to running multiple instances of application servers as I > am). From what I understand, with the J2EE version, you do > not start and stop ColdFusion itself, you start and stop the > app server (or instance that CF is running on).
This is really no different than how the "regular" version of CF MX works, though. When you install the standalone version, it installs a subset of JRun, and when you start the "ColdFusion MX Application Server" service, you're starting this executable: "C:\CFusionMX\runtime\bin\jrunsvc.exe". > Additionally, the fact that ColdFusion is no longer using > the registry to store data (on Windows of course) is yet > another major architectural difference. I think this is true for any version of CF MX, though, whether it runs with its own bundled J2EE app server engine or whether you install it on your existing copy of JRun or WebSphere or whatever. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
