I have a question. I want to create a multi-module app using the default style created by start.vaadin.com.
Where the elements shown on the left are modules, rather than views from a standard project.
Is there an example of something like this?
There is no example available as far as I know, but it’s pretty straight forward and simple.
Only thing to consider: ensure that your packages are either below your main application’s Application.java or customize / add @EnableVaadin and configure all packages to be scanned
It’s a shame there aren’t any examples. They’re particularly useful and would be great in a case like this.
But we must make do with what we have.
Thank you very much.
I usually don’t split the project this way because it’s difficult to create navigation between modules. Since I’m creating a backend module then it leads to the question, do I want one backend/service module per view module? ( Usually no it’s not working well).
So most of the time I have one backend module, one frontend and then I can have an addon module/reusable components.
I’ve seen both approaches. If you use DDD where each domain has its own package / module - this approach is really good for separation and different teams. Just cross communication between those modules / linking is harder but it allows for good maintenance for really laaaaaarge projects
By “multi-module”, do you mean a maven multi-module project?
If so I also assume the target is one ear with multiple wars?
That is what we have, and it’s been a constant fight to get Vaadin to behave.
It’s doable, but we never know if something will break in the next version.
Main issue seems to be the dev mode, which expects there to be one source directory.
We’ve gotten around that by dropping dev mode.
Then we don’t get the fancy new ai stuff, but that’s fine by me.
1 Like