nope, gotta be hardcoded (returntype, type, and extends are compile-time attributes, so you cannot use a request (or any) variable in them).
I'm pretty sure I think that it is a good thing, as it forces you to logically structure where your CFCs go and adhere to that standard, across sites, apps, whatever. -dave >>> [EMAIL PROTECTED] 5/7/2004 10:21:10 AM >>> Can I now do the following as a valid return type: returntype="#request.cfcmapping#._model.page where request.cfcmapping is changed on a 'per site' basis - I don't really want to hardcode the value thanks, john. ********************************************************************** Copyright ERA Technology Ltd. 2004. (www.era.co.uk). All rights reserved. The information supplied in this Commercial Communication should be treated in confidence. No liability whatsoever is accepted for any loss or damage suffered as a result of accessing this message or any attachments. ********************************************************************** _____________________________________________________________________ This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
