Interesting. I think this is not really the result of how ColdSpring creates aop proxies (which are proxies of the beans, btw) it is really perhaps the result of how cf works itself. In reality since there is no such thing as a cfc 'object', and all the methods you define for a cfc become their own command objects anyway, it mayt seem that there there really only ever is a proxy of a collection of methods, as opposed to a true proxy of an object. Maybe I can try to introduce a concept of a 'caller' object to try to alleviate this

Chris


On Oct 25, 2006, at 12:31 PM, Barney Boisvert wrote:

I hadn't noticed before, but ColdSpring proxies proxy the methods of a
bean.  This is unlike Spring's proxies, which proxy the bean itself.
Here it is in pictures (might need to copy to a fixed-width-text
viewer):

ColdSpring:           Spring:
+-bean-----------+    +-proxy----------+
| +-proxy------+ |    | +-bean-------+ |
| | +-method-+ | |    | | +-method-+ | |
| | |        | | |    | | |        | | |
| | +--------+ | |    | | +--------+ | |
| +------------+ |    | | +-method-+ | |
| +-proxy------+ |    | | |        | | |
| | +-method-+ | |    | | +--------+ | |
| | |        | | |    | +------------+ |
| | +--------+ | |    +----------------+
| +------------+ |
+----------------+

The manifestation of the difference is that invocations of methods
within the same component do NOT go through the proxy with Spring, but
they do with ColdSpring.  I'm not sure if this is an intended
difference, but it caused me some problems (mostly because I expected
it to work the way Spring does).

cheers,
barneyb

-- 
Barney Boisvert
360.319.6145

Got Gmail? I have 100 invites.


Reply via email to