William,
Maven tiene un catalogo de arquetipos, y entre ellos unos que relacionados con vaadin;
$ mvn archetype:generate
>84: remote -> com.vaadin:vaadin-archetype-addon (-)
85: remote -> com.vaadin:vaadin-archetype-application (This archetype generates a simple Vaadin application as a Maven project.)
86: remote -> com.vaadin:vaadin-archetype-clean (This archetype generates a simple Vaadin application as a Maven project.
No custom widgetset is included.)
87: remote -> com.vaadin:vaadin-archetype-jpacontainer (This archetype generates a simple Vaadin application using JPAContainer as a Maven project.)
88: remote -> com.vaadin:vaadin-archetype-portlet (This archetype creates a simple porlet with required Vaadin dependencies. In addition to standard JSR 286 configurations the archetype also adds liferay specific configuration files, but they shoudn't affect other portals.)
89: remote -> com.vaadin:vaadin-archetype-sample (This archetype generates a Vaadin application as a Maven project.
The application contains a custom GWT widgetset that is compiled
by the GWT compiler and integrated into the project as part of the
build process. The application is based on the Vaadin Color Picker
90: remote -> com.vaadin:vaadin-archetype-touchkit (This archetype generates a simple Vaadin application using TouchKit as a Maven project.)
91: remote -> com.vaadin:vaadin-archetype-widget (This archetype generates a Vaadin widget project for Vaadin 7.0 and a test application.)
92: remote -> com.vaadin:vaadin-maven-plugin (Maven plugin for Vaadin.)
93: remote -> com.willowtreeapps:oak-archetype (-)
eso te generara tu esqueleto de tu applicacion en vaadin mavenizada, tu puedes inyectar tus EJB en cualquier momento, pero podrías ser mas especifico acerca de la selección de estas herramientas? (usualmente la selección de los frameworks a usar se hace despues del diseño :) )
Adolfo