Thanks guys!  I must apologize as I was trying to condense post. . . but we 
have actually tried these exact methods.

Let me give you a better idea of our folder structure:

wwwroot
  - testfolder
      - user
        - username1
          - OurApplication
              - subfolder1
              - subfolder2
                 - Application.cfc
              - subfolder3
              - Application.cfc
              - ApplicationProxy.cfc
        - username2
        - username3
  - testfolder2
  - testfolder3
 
So we have tried using the Proxy file and that uses cfextends to grab the 
OurApplication root Application.cfc file.  The problem is it still tells us it 
can't find the ApplicationProxy component.  However if we move the whole 
"OurApplication" folder to the wwwroot level (equal to tesfolder, testfolder2, 
testfolder3, etc) it works fine.  So it appears that our application would have 
to reside at the wwwroot folder to use this method, which isn't possible for us.

I'm not very familiar with mapping. . . would we have to do one for ever 
username folder?  Each username has its own instance of the the application for 
testing and development (since we are developing lots of subapplications at one 
time).  Obviously if we had to map for every possibility and as we move through 
the life cycle that would be difficult.

Anyway thanks for the help all.  The articles have been very halpful and 
hopefully we're on the right track. . . its just a matter of figuring out how 
to make it work for those root Application.cfcs that are lower than the 
wwwwroot folder.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Deploy Web Applications Quickly across the enterprise with ColdFusion MX7 & 
Flex 2
Free Trial 
http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJU

Archive: 
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:274168
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4

Reply via email to