On 5/12/05, Phil Rasmussen <[EMAIL PROTECTED]> wrote: > Hi Jason, > > I have also noticed a similar thing when using instance manager from within > CF7 admin. I am much more comfortable using the Jrun4 Admin and creating my > new CF instances that way and then deploying them as an extracted ear/war > under the jrun4/servers directory. I have a jrun-web.xml under each of my > server instances now and it all behaves as it should. At least this way i > jave full control over what the J2EE server is doing, rather than the cut > down wizard style used by the CFadmin..
I agree whole heartedly Phil. Jrun Admin gives you much more presise control over thiings. However, the cf instance manager is very convienient in the way it automatically deploys a new cfinstance to the new jrun server. The only issue I've come across so far is the problem with the jrun-web.xml file not being included, but that's easy enough to create. The best plan of attack from my point of view is to create all your instances with the cf admin and then manage them as usually with jrun admin and xml files. You can adjust most of the settings in the xml without ever having to use the jrun admin. -- Jason Sheedy www.jmpj.net --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
