Hi!
We have at our company now a very common, simple way to build our screens.
Of course the MVC pattern is implemented and the topology is something like that:
- M: EJB based data access
- C: servlet based controller classes (1 main servlet - N controller classes)
- V: plain HTML + JS generated by own Java “HClasses” every time (the whole page is refreshed…)
And we would like to enhance this operations so thats why i am interested in Vaadin.
I like it very much but I am not sure its for us, please help me!
As I see so far Vaadin is a bit of a monolith kind of system. I mean when you work in
Vaadin you start to create your application basicly as a screen and then write the
controller layer through creating the “Listeners” in the same class, etc. But we have a
lot of smaller screens called maintainer screens, lets say a 100 of them. So there is a
main servlet who delegates the controlling to the appropriate (actual) controller class.
Most of the screens just manage the simple CRUD operations and some of them the complex BL
but the thing is: they are very generic and similar to each other, so we have a generic
solution to render these screens so most of the time you dont have to deal with the “V”
layer at all. But now we dont have fancy components like in Vaadin and not even AJAX, etc.
My question is: if we would like to use Vaadin only as a extended, rich “page renderer engine”
can we do that? Without have to pass this kind of multiscreen controller structure to the “V” layer.
Thanks is advance!