As far as I know, a context root is the definition of an application within J2EE much like say a website in IIS terms or a application definition for ..NET in IIS.
I think, that they must be unique. "This e-mail is from Reed Exhibitions (Gateway House, 28 The Quadrant, Richmond, Surrey, TW9 1DN, United Kingdom), a division of Reed Business, Registered in England, Number 678540. It contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you have received this communication in error please return it to the sender or call our switchboard on +44 (0) 20 89107910. The opinions expressed within this communication are not necessarily those expressed by Reed Exhibitions." Visit our website at http://www.reedexpo.com -----Original Message----- From: Rick Root To: CF-Talk Sent: Tue Nov 14 20:32:38 2006 Subject: Coldfusion, flex, multi-instance setup and context root Can anyone explain to me what the meaning of "context root" is, and how it pertains to a multi-server installation of coldfusion? And how it's related to the document root? I have a setup where I have one web site that is configured to use a "primary" coldfusion instance.. let's say "instance1". And a subdirectory called "tools" is configured to use a "secondary" coldfusion instance, named "instance2" From a coldfusin perspect everything works fine. Calls to http://localhost/tools/index.cfm are handled by instance2, while calls to http://localhost/index.cfm are handled by instance1. However, when I added flex to the mix, things get much more complicated. If you look at the CFROOT/flex/services-config.xml file for each instance, the endpoint for the flex gateway is the same. <endpoint uri="http://{server.name}:{server.port}{context.root}/flex2gateway/"; class="flex.messaging.endpoints.AMFEndpoint"/> But for both instances, the context root (configured in the META-INF/application.xml file is "/" .. and since both instances are operating on the same hostname and same port in this case.. the endpoint is the same. Changin the context root for instance2 causes all kinds of havoc.. I tried changing it to /tools and /tools/ .. but that completely broke coldfusion. So I ended up editing the services-config.xml file for instance2 so that it lookedl ike this: <endpoint uri="http://{server.name}:{server.port}{context.root}/tools/flex2gateway/"; class="flex.messaging.endpoints.AMFEndpoint"/> And then I had to add "-context-root /tools" to my flex compiler options - even though that's NOT the context root according to the application.xml. It owrks though. Any techie's out there who really understand this stuff want to try to explain it all to me? :) Rick ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:260415 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
