At 03:21 PM 2/28/2003 +0000, you wrote:

>I'm still trying to work out how I can build on CFC's for my new site
>template system, and I was worried to read something on the list recently
>saying that CFC's have problems calling methods in parent components.
>
>Say I've got a 'people' DB table, with general info on people whether
>they're admins, users, contacts, whatever. Then I have a 'users' subset
>table containing user-specific infos. Using the MVC pattern I'm trying to
>follow, this would be reflected in a person.cfc, and a subtype user.cfc.
>(This particular example might not be implemented, but it serves to
>illustrate my point.)
>
>Obviously the advantage of CFC's is that I can updateUser() or whatever, and
>have that method call the updatePerson() method if necessary. Can this not
>be done?

If you use the extends attribute, you call methods in the PARENT cfc from 
the CHILD cfc. As for CFTRANSACTION, I'm not aware of any problems. I could 
be wrong, but if you're calling an inherited functions that contains a set 
of CFTRANSACTION tags, there should not be an issue because of the way CFCs 
are compiled. It's not like your calling 2 custom tags, with the opening 
CFTRANSACTION tag in the first, and the closing CFTRANSACTION tag in the last.




>This obviously impacts on the use of CFTRANSACTION - I've seen a few
>mentions of problems with this. Can a transaction not span multiple CFC's?
>
>Gyrus
>[EMAIL PROTECTED]
>work: http://www.tengai.co.uk
>play: http://norlonto.net
>PGP key available
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription: 
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm

                                Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
                                

Reply via email to