Hi >You/I/we create a Interception Facility, that defines one or more interfaces >for interceptors. That sounds like the logical first step.
What Rickard was saying was that he used not only the Interception Aspects (explicit with theknowledge of the component like you are proposing, and from outside like real pointcuts) but mostly the Introduction/Mixin things. The point he made was that the big shifting comes with the Mixins/Introductions of interfaces/behaviour via AOP. The Objects are stripped of all functionality, and that is introduced via AOP mixins vertically. Of course, that was a bit extreme but there is a point to chopping up the objects into functional bits (as Avalon Framework already does), declaring these as Interfaces but even chop up and centralize the implementation via aspects, both interceptions and introductions. So the whole pictyre is probably a combination of the Interceptor framework and an "Introduction Framework" that I tried to describe (not reeally thought through!) wdyt? /peter --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
