Hey, I'm working on removing dependencies to the runtime. This basically involves creating interfaces in SPI that code can use instead of going directly to e.g. ModuleModel. This is easy. But, there needs to be a place to invoke the visitor on the application. Currently we have ApplicationInstance in runtime which can do this. We also have Application in API, but it cannot be handed an SPI class (of course).
So, one question is why we have Application/Layer/Module in API in the first place. These indicate that the code using these have an understanding of Qi4j and is not only trying to implement some domain code, so it might be an idea to move these to the SPI instead, in which cases it would be natural to add the model visitor to Application. Does this make sense? If not we can simply introduce ApplicationSPI in SPI, but it seems unnecessary.... /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
