I didn't find anything specific in the docs. However, you might want to look at this:
JRun4_root\docs\html\Assembly_and_Deployment_Guide\deploy3.html >From my experience I would set up an expanded directory when developing an app and >then create the war or ear file when ready to deploy. Ted Zimmerman -----Original Message----- From: Drew Falkman [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 11:51 AM To: JRun-Talk Subject: RE: JRun 3.1 -> 4.0 Woes This might be in the docs, but what is the best practice approach for developing sites? Does Macromedia recommend that we code to a directory under the root on the dev server, then deploy (war, ear, etc) to other servers? -Drew -----Original Message----- From: Theodore Zimmerman [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 6:38 AM To: JRun-Talk Subject: RE: JRun 3.1 -> 4.0 Woes Hi Stephane, You are correct in that JRun 4 doesn't expand the war file under the servers/default directory. However, if you look in the SERVER-INF/temp directory you will see your web application and if you expand that you'll see the directory structure you are familiar with. These files aren't for editing. One thing you could be running into is that JRun 4 will automatically use the war files name for the application's url mapping. So if your war file is named myapp.war then the url mapping automatically becomes /myapp. To get around this you would have to set the <context-root> attribute in the jrun-web.xml file in your applications WEB-INF directory. You'd have to do that prior to rewarring the file and then deploy again. Take a look at the following in the doc set: JRun4_root\docs\html\Assembly_and_Deployment_Guide\descriptors4.html JRun4_root\docs\html\Installing_JRun\migration3.html D:\JRun4\docs\html\Assembly_and_Deployment_Guide\assembly3.html Also instead of deploying as a war file you could just take your entire directory structure and and copy it under the server's root directory. HTH. Ted Zimmerman -----Original Message----- From: Stephane Plante [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 19, 2002 4:04 PM To: JRun-Talk Subject: JRun 3.1 -> 4.0 Woes Can anyone please help me with the following scenario: [Using JRun 3.1 and Apache 1.3.24] I have a .war file that I use on JRun 3.1. Now, when I deploy on JRun 3.1, (say, in servers/default) it would expand the .war file there. I then made references to these files in a few Apache directives (for caching and whatnot). [Using JRun 4.0 and Apache 1.3.24] Now, this same .war file, when "deployed" in JRun 4.0, does NOT expand the war-- although it has been successfully deployed. This is bad for me since I need to have these files expanded in servers/default. In addition, once this web application is deployed, I cannot connect to JRun 4.0's default server to fetch any pages. I'll get 404's- probably because those files weren't expanded. Any help would be appreciated! Thanks, Stephane ==================================== Stephane Plante [EMAIL PROTECTED] http://www.speechworks.com ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
