Java – GWT clientfactory: isn’t this just a huge blob / monolith?

GWT clientfactory seems to be a new design pattern for GWT applications. Although GWT API has not officially become a part of GWT API, it is encouraged by GWT and found in countless GWT / MVP examples

I want to like the clientfactory concept But what I worry about is: for a really large application, it has many screens, display areas and complex architecture. A single clientfactory will become a huge whole of the data structure, and there may be hundreds of getter methods

So I asked: is this OK? Why does this overall design encourage and accept GWT rather than other (general) applications More importantly, is there a way to decompose the extensive clientfactory into a hierarchy of factory objects to help code maintainability, dependencies / references, etc?

If so, will the clientfactory be broken down into smaller factories, each responsible for injecting the necessary views, presenters, etc. into different parts of the application?

Solution

The idea of clientfactory is only manual Di to realize easy to understand cabling Without knowing gin or even GWT, these applications seem to be mainly Java, which lets you know how to make work without knowing the details of the author's preferred way to connect applications together

Like an example, the Java Tutorial lets you start with public static void main (string [] args), or you may build a completely manual servlet, which you can use to get ideas and then turn to better structured applications Clientfactory's utility stems from its simplicity and transparency as a concept, not because it is the only way to build large applications