Clean Architecture Application with Vaadin Flow

[sator.stefan (Stefan Sator)]

Hello Petter,
Thank you for your detailed reply. I have been ill for the last 10 days and have only just got round to reading your reply.

I would like to go into the following two points in more detail:

@Petter

If you think of a view as a user interface component, then the view model should be passed as a constructor parameter. On the other hand, if you think of a view as a Vaadin route, it makes sense to let the view create the view model and pass it on to the other components. Sharing data between views should not happen through a shared view model, but through some other means, such as URL parameters or immutable data objects stored in the session.

What do you mean with “On the other hand, if you think of a view as a Vaadin route,”
Why does it make a difference? Currently I dont pay any attention to routes at all. They are just there and I dont think of them at all. How would that change if I start thinking about them?

From the article: Is MVP a Best Practice? | Vaadin

If the UI consists of different components that show different views of the same data, it is not the presenters that need to communicate with each other. In that case, the components need to share a common model. Which brings us to the next section…

Why would different components ever show the same data? Can you give an example?

Best regards
Stefan