On Thu, Feb 12, 2009 at 9:42 AM, Michael Hunger <[email protected]> wrote:
> I would also propose the declaration at assembly time. This makes the stuff > explicit. Yes, it is only possible to add these things during assembly. > Perhaps we'd like to be able > to restrict the available SideEfffects / Concerns with AppliesTo Filters at > the Entity, where the developer could > disallow (include/exclude) certain stuff from its composites? Which Composites that are candidates for these concerns/sideeffects, is just the initial constraint. The AppliesTo filter mechanism will still be evaluated, and during our conversations we assumed that both AppliesTo declared to the Concern itself as well as explicit assembly-time AppliesTo would be evaluated; module.addEntities( AbcEntity.class ).withConcerns(SomeConcern.class).appliesTo( SomeAppliesToFilter.class ); or similar. > This could not only applied to the UI part but also in other parts of the > application where a "Context" (perhaps this is > already what we are talking about here at the assembly level !!!! ) adds > certain concerns/sideffects to the entities in > place. Agree. > What would be nice is adding the stuff also in a more general way. E.g. I > want to add the stuff to all composites > implementing a certain interface or to all services or whatever. So there > filters would come handy. That would reduce > the tedious and manual task of adding the same stuff to (e.g. all entity > composites that shall be used with this > additional functionality). Or is this tooo magic AOP like ? We have also discussed to add "getters" on the ModuleAssembly, LayerAssembly and ApplicationAssembly classes, so that you can iterate through the assembly declarations and make the application of concerns/sideeffects a programmatic exercise. This is good for instance to add Tracing on a whole system. > What about the mixins necessary for the SideEffects/Concerns. Besides having > those that are declared at the SE/C > interfaces. If I'd like to have slightly different mixin implementations, > where would I declare them? Interesting question. For Property only mixins, there is automatic support in the PropertyMixin, but for custom implementations --> I don't know. Possibly add those through the fluent API at assembly as well? Cheers Niclas -- http://www.qi4j.org - New Energy for Java _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
