To get a clear answer you have to rephrase your question, explaining what problem are you trying to solve.
If what you want is to create MVC model instances, keeping the details of the creation in one coding module, then yes this is absolutely meaningful. Actually, even then I would create a container interface MVCModel
which would have tree properties, a Model
, a Controller
and a View
. The MVCFactory
would have one create function which would instantiate an MVCModel
object.
public interface MVCModel{
Model getModel();
View getView();
Controller getController();
}
public abstract class MVCFactory{
public abstract MVCModel createModel();
}
Hope I helped!