On Tuesday 15 April 2008 20:24, Rickard Öberg wrote: > These would be the most interesting ones I think as it allows in > particular UI's to see things from the "Domain perspective". The problem > I see with it is that if a UI-module A is allowed to access a Domain > Composite B in another Module, but not Infrastructure which B can > access, then doing moduleForComposite(B).lookupService() by A is a way > to get around the visibility rules (which would be the benefit at the > same time). Is this ok is the question?
I think this is the equivalent to the AccessibleObject.setAccessible( true ), for reflection code to circumvent private methods and fields. Other than that, go ahead with what you feel is best. Cheers -- Niclas Hedhman, Software Developer I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
