Hey, Currently it is possible inject the ModuleBinding of a object/composite by using "@Structure ModuleBinding module". However, ModuleBinding is an SPI object so it's not very clean, and I am also leaning towards wanting to have access to ModuleInstance methods in application code. Specifically I want to be able to ask the Module for the owning Module of another Composite type. This is done typically to be able to ask for services from that Composite's "perspective", such as looking up the EntityStore for a particular Composite.
So, I would like to introduce an API interface org.qi4j.structure.Module to be implemented by ModuleInstance and which contains the methods that we specifically want to expose to application code. This will include methods from ModuleInstance down to ModuleModel, which will also help hide this from the application code. Does this sounds like a good idea? If yes, what methods from ModuleInstance down to ModuleModel should be included? Also, if yes, then support for "@Structure ModuleBinding" will be replaced with "@Structure Module". /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
