kumm
commented
6 years ago For using @Inject you have nothing to do. As you can see in readme:
"Introduce addon as a dependency, and start using @Inject in your route targets, or layouts."
Nothing special.
Since MainView from the tutorial is a route target, just @Inject.
Of course you should replace constructor with a @PostConstruct method to be able to use your injected beans there.
And don't forget to deploy on a jee7 container. You see jetty in vaadin demos, it won't work. Currently TomEE, Wildfly, and Payara are tested, but should work on any compliant jee7 container.
I am going to look for a proper way to publish some demo app, or apps.
chrisowensboston
As a Vaadin noob, I could use either a concise instruction or a snippet of example code. I am very familiar with CDI and related concepts but I know nothing about the Vaadin scopes.
For example, how would I modify the MainView class in the Vaadin Flow Tutorial to allow @Inject to work?
Also, I have a bunch of ejb @Stateless beans that are part of an imported module that is not Vaadin aware. How would I make them available for injection in a Vaadin view?
The use case, I imagine, is pretty common: consider a DAO or any back-end service that is implemented as an EJB but is not Vaadin-aware; I'd like my GUI components to be able to get hold of an instance or proxy by injection.