On 1/24/06, Barry Beattie <[EMAIL PROTECTED]> wrote: > I always assumed it was better to create a "facade" cfc for the > webservice which then calls down into the business logic cfc's (much > like facade cfc's for flash remoting). in this case the issue with the > additional cfproperty tags (in the core business objects) is not an > issue
OK, there's a misunderstanding here about how <cfproperty> works... You have a facade CFC which provides the actual calls. That does not need <cfproperty>. Suppose one of the methods returns a complex type (or takes a complex type as an argument). You write a CFC for that complex type and *that* CFC uses <cfproperty> to describe the (public) attributes of the complex type. Essentially the CFC is a "typed struct". Does that clarify? -- Sean A Corfield -- http://corfield.org/ Got frameworks? "If you're not annoying somebody, you're not really alive." -- Margaret Atwood ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] 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/[email protected]
