I have been running cfmx7 server configuration a while but wanted to test the
features in the multi-server config. I simply installed it and migrated my old
settings etc and things really worked fine. The only thing I wonder a bit about
is a strange problem with the flash gateway to find my cfc's. Earlier I kept
them in the cf wwwroot/-dir and flash remoting for both my virtual domains
worked fine. After upgrading to multi-server I have to put the CFC's in the
virtual domains dir in order for the gateway to find them. Have tried to add
mappings and also tried adding a custom tags path with no luck.

Is there something I've missed? Do I really need to put the cfc's in my
http-enabled dir?

AG

CFCs that handle remoting requests have to be web-accessible, i think that's
always been the case. if you want to centralize them you might build remoting
facade CFCs that in turn talk to your "real" CFCs in a mapped dir.

Thanks for the reply. Still scratching my head here and would just like to
explain the situation a little deeper to assure I fully follow.

Older installation:
CFC's in /opt/coldfusionmx7/wwwroot which was in the CustomTags path.
Calls to cfc's from templates wihtin different virtual domains on the server
worked fine, also via flash remoting when calling netservices as
http://<virtualdomains>/flashservices/gateway.

Upgrade to muliserver config:
CFC' in /opt/coldfusionmx7/wwwroot which is in the CustomTags path.
Calls to cfc's from templates wihtin different virtual domains on the server
works fine if not called via flash remoting which give not found errors.

The above is what makes me a little confused nad I'm trying to understand.
Especially I don't like keeping the cfc's in the actual http-path... :)

as i said, you don't have to keep the "real" CFCs in a web-accessible path
though you do have to use facade CFCs (which i gather is a good practice
anyway) to handle the flash remoting/talking to the "real" CFCs. remoting CFCs
have to be web accessible and
http://livedocs.macromedia.com/coldfusion/6.1/htmldocs/buildi12.htm seems so
say this has always been the case for mx.