Michael Hunger wrote:
I think I like the approach of having the UnitOfWorkConcern applied to
my service's methods.
Would it be sensible to also allow a class (~Composite) as target for
the annotation so that all public methods of the Composite get the
Concern applied?
That would work. AFAICT it would only require a change in the
AnnotationAppliesToFilter.
Hmm was looking to subclass the Concern to add another AppliesTo that
includes a custom filter or my service composite, but the concern is final.
How would I otherwise have a existing (final) concern be applied to a
range (or all) of the methods of a certain composite without adding the
original AppliesTo target annotation (@UOWPropagation in this case) to
each of these methods.
The main problem here is that the class is final, and it shouldn't be.
IMO there's a bit of trigger-happiness going on with the "final" keyword
in the codebase. "final" is good, but don't overuse it. This is one of
those cases. I've changed it for this concern now.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
