Re: [CFCDev] How to use returntype correctly

[Jason Daiger]

Dave, Is this true even if you go through a service layer?  Also, can you provide any links or references on this issue w/ Flex2?  I'm not designing in Flex 2 at the moment but our long range plan for the UI is to migrate various pieces of the app to Flex2. So since the app is in development now, changing to a fully qualified path now is much easier.  I'd just like to understand the why. Thanks, Jason Dave Carabetta wrote: On 3/17/06, Cliff Meyers <[EMAIL PROTECTED]> wrote: I didn't suggest setting the type/returntype to "any"; I just suggested using an unqualified component name ("User") instead of a fully-qualified component name ("com.company.app1.User"). It should only be an issue if you have two CFCs of the same name in different packages. That seems like a fair compromise between using a fully-qualified component name and type/returntype="any". Due to the requirements of accessing CFCs in Flex 2, I would use the fully qualified path rather than the abbreviated name if you even *think* you might use Flex 2. This way, you're more forward-thinking and reduce any potential headaches down the road. At the very least, if you're not going to use the component name, return the built-in default object reference, as I discuss here: http://www.cbetta.com/blog/index.cfm/2005/12/9/return-type-for-returning-cfc-instances Regards, Dave. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/cfcdev@cfczone.org -- Jason Daiger URL: www.jdaiger.com EML: [EMAIL PROTECTED] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/cfcdev@cfczone.org