Just reading Mark's presentation - Just to clarify, my code in the
first post is being done in the onApplicationStart so I don't know if
that counts as parenting as you mentioned Tom. I see Mark shows an
example of a CFC being declared in the init() method of another CFC
which I'm not doing. I'm initialising each one separately in
Application.cfc and then manually managing the use of those methods in
my model i.e.
application.com.com1 = createObject("component","com.com1").init();
application.com.com2 = createObject("component,"com.com2").init();
So if I needed a method from com2 I would do something like this:
request.com1 = application.com.com1.getMethod();
request.com2 = application.com.com2.getAnotherMethod(request.com1);
So if I added an extra argument to the method / init in com1 I'm a bit
unsure how that would affect com2 if I'm just passing the result as my
argument - I'm just trying to understand where the dependencies are
coming from here.
----
Again with the super approach.
If com3 were to extend com1 and I added another argument to a called
method in com1 fair enough I can understand me possibly having to
change any calling methods in 3 (or any other CFCs which are relying
on this) and from that point of view I can see the benefits of having
CS but this goes against what is being suggested in the example:
http://www.coldspringframework.org/coldspring/examples/quickstart/index.cfm?page=intro
I hope that makes sense because I'm getting a bit confused :-|
Thanks again,
James
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"CFCDev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cfcdev?hl=en
-~----------~----~----~----~------~----~------~--~---
